I will be using the computer, and it will blue screen with no apparent reason. I am at a loss as to what is causing this. The computer does not give me any warning, strange behavior, or explanation after reboot. I have a Dell 14r running Windows 7 home premium 64bit. I found the .dmp, but have no idea how to open said file.

Hi.. Sounds like memory Problem. Try to run memory test with MemTest Check ur Dump File with WhoCrashed to give a full report. Give ur Feedback to help you.I want to be a MVP! | Computer Technician - MCITP Enterprise Administrator 2008

You should check the event log to see if there are any hardware errors in the logs. Also I would run a chkdsk and the built in memory testing software. You can ask the memory testing software built into windows 7 by searching for Windows Memory Diagnostic. I would suspect memory first.

Is there any way I can upload the .dmp file and someone would be able to ascertain the situation? I ran the whocrashed file, and here are the five most recent results. On Mon 7/16/2012 9:13:09 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\071612-20592-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880058B1FB5) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/16/2012 9:13:09 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880058B1FB5) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/16/2012 9:10:22 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\071612-21231-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005890FB5) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/16/2012 1:38:03 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071512-22573-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005896FB5) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/16/2012 1:35:03 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071512-19718-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005861FB5) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Maybe your problem is a bad driver. Did you add new hardware recently, updated any drivers or did any special changes recently. if this just recently started you can use the "Use last known good configuration" feature at the startup if you press F8 before the windows logo screen appears. select a date prior to your problem. You can also run the command sfc /scannow in elevaded command prompt window to check if os files are okay.

No new hardware or driver changes. The only thing I can think that would be related is two Microsoft Virtual WiFi Miniport adapters. In the past, my machine was BSOD'ing at a couple of times a night. A friend noticed these had drivers that were disabled, and he deleted them, and the issue stopped. These virtual adapters have kept reappearing, I think they are related to Intel My WiFi adapters on my machine. Though, I dont know if that is fixing the issue.

Can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via Windows Live SkyDrive or similar site? The following link has information on using Windows Live SkyDrive: http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop Also, you do not necessarily have to zip up the minidump files, you can upload them one at a time.

https://skydrive.live.com/redir?resid=57319ED3A0E5AF31!123&authkey=!ALH8NE46V0Np8yY Is this right?

The link worked great. The minidump files showed a DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) stop error caused by the NETw5s64.sys: BUCKET_ID: X64_0xD1_NETw5s64+13fb5 The NETw5s64.sys, which is a driver for Intel wireless, may have become corrupted so try uninstalling and then reinstalling the Intel wireless driver. You can use the following utility to see if there is an updated driver available from Intel: http://www.intel.com/p/en_US/support/detect/wireless