Random BSOD's

x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes
- an OEM or full retail version? Full Retail

- What is the age of system (hardware)? Everything is new
- What is the age of OS installation: 2 Days

I'm having random BSOD's at any time. I can play games for two-three hours without one but I can also startup my computer and have one three minutes later. Most times the computer doesn't even throw me a BSOD, and just freezes, becoming completely unresponsive until I hard reset it.

Thanks for your time.

I looked at the the three dumps files and two of them are error code 124. The oldest dump is error code 50. Both of these are hardware indicate hardware problems.

Please read this article on your bugcheck 124: [2-Int] Stop 0x124 - what it means and what to tryDownload a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes. Here is a good thread on Memtest: Memtest86+ Guide/How To's - Overclockers Forums

Do a CPU stress test as well, using Prime95.

Test your temps with Speedfan.

Drivers can also cause both a 124 error and a 50 error. Older drivers can and do cause memory corruption and crashes. You have the following out of date drivers on your system:

jswpslwfx.sys Thu May 15 06:28:50 2008 - D-Link USB Wireless Adapter DriverD-Link - Tech Support Product List. This driver is seriously obsolete. Update it or upgrade your wireless adapter.

scmndisp.sys Wed Jan 17 02:48:03 2007 - NDIS User mode I/O Driver is a driver file belonging to product ® Neutral Wireless Solution. I think this may be a Netgear driver. It is way obsolete for windows 7. Update the driver if you can or uninstall the hardware/software it is associated with and upgrade.

After you take care of these two drivers, reboot and see how your system runs.

Ken posted while I was typing. Follow his advice then take care of the drivers. Those two drivers will cause instability of your system.

Keep in mind that error code 124 in most definitely hardware related and error code 50 also points to hardware. It is most likely not a Win 7 problem. Unless we are really lucky, most times the dumps do not point out an exact cause; but they give us clues as to where to start trouble shooting. Troubleshooting is an elimination process. You start with eliminating known BSOD causes and keep going until the problem is solved.

I am glad that your hardwareware tests did not show errors for RAM, the CPU or the GPU. How may passes did you make with Memtest 86? You need at least seven passes. Did you take care of those two very obsolete drivers either by updating or upgrading? Freezes are most frequently cause by the GPU followed by the LAN adapters, wireless adapters, and sound cards. Are you over clocking anything? If you are, please revert to default values.

I have a NVidia video card with which I had to try five drivers to get the one that stopped my freezes. However, I knew it was the video card that was causing the freezes. It showed up in the system events. I ended up using the third or fourth driver down the list.

Now that you have updated drivers, run this tool again, https://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html, and upload your latest system information for us. We can take another look and maybe pin point something. I know you haven't had another BSOD; but the updated system information may help.

Was this crash before or after you reinstalled your Netgear adapter? I still see these drivers:

jswpslwfx.sys Thu May 15 06:28:50 2008 - D-Link USB Wireless Adapter Driver, D-Link - Tech Support Product List. This driver is seriously obsolete. Update it or upgrade your wireless adapter.

scmndisp.sys Wed Jan 17 02:48:03 2007 - NDIS User mode I/O Driver is a driver file belonging to product ® Neutral Wireless Solution. I think this may be a Netgear driver. It is way obsolete for windows 7. Update the driver if you can or uninstall the hardware/software it is associated with and upgrade.

All of the rest of your drivers look good.

Error code A, IRQL_NOT_LESS_OR_EQUAL - usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Code:

Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Sun Sep 19 22:42:30.396 2010 (GMT-4)
System Uptime: 0 days 0:00:07.552
Loading Kernel Symbols
...............................................................
......................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002ef72b3}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ef72b3, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310f0e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02ef72b3 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff88003362060 -- (.trap 0xfffff88003362060)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a003bf9f8c rbx=0000000000000000 rcx=0000000000000000
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031b48e0 rsp=fffff880033621f0 rbp=fffff88003362620
 r8=fffff8a0000354e0  r9=000000000000ffff r10=0000000000000008
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!CmpFindValueByNameFromCache+0xe0:
fffff800`031b48e0 428b14b8        mov     edx,dword ptr [rax+r15*4] ds:fffff8a0`03bf9f8c=????????
Resetting default scope

LOCK_ADDRESS:  fffff800030db400 -- (!locks fffff800030db400)

Resource @ nt!PiEngineLock (0xfffff800030db400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff800030db400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002ed6ca9 to fffff80002ed7740

STACK_TEXT:  
fffff880`03361aa8 fffff800`02ed6ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03361ab0 fffff800`02ed5920 : 00000000`00000000 fffff980`03d84ee0 fffffa80`05b36040 00000000`002c8788 : nt!KiBugCheckDispatch+0x69
fffff880`03361bf0 fffff800`02ef72b3 : 00000000`00000001 fffffa80`05b0c040 00000000`00000001 fffff800`02e77a28 : nt!KiPageFault+0x260
fffff880`03361d80 fffff800`02eb40c7 : 00000000`00000001 40000000`00002020 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`03361e50 fffff800`02eb4487 : fffff8a0`00022010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`03361ed0 fffff800`02ed57c5 : fffff8a0`06675a70 fffff8a0`00022010 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0xd7
fffff880`03362060 fffff800`031b48e0 : fffff8a0`00022010 00000000`003a7f88 fffff8a0`000354e0 fffffa80`06800000 : nt!KiPageFault+0x105
fffff880`033621f0 fffff800`031b31a6 : fffff8a0`06675a70 fffff880`033624e0 fffff880`03362320 fffff880`03362328 : nt!CmpFindValueByNameFromCache+0xe0
fffff880`033622c0 fffff800`031b2933 : 00000000`00000000 fffff880`033624e0 fffffa80`00000001 fffff980`01554f80 : nt!CmQueryValueKey+0x136
fffff880`033623a0 fffff800`02ed6993 : fffffa80`05b36040 fffff880`03362758 fffffa80`00000001 fffff980`01554f80 : nt!NtQueryValueKey+0x381
fffff880`03362530 fffff800`02ed2f30 : fffff800`031483bb ffffffff`80000110 00000000`00000001 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03362738 fffff800`031483bb : ffffffff`80000110 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff880`03362740 fffff800`032c290a : fffffa80`06f66390 fffff880`03362c10 00000000`ffffffff 00000000`00000000 : nt!IopGetRegistryValue+0xab
fffff880`033627a0 fffff800`032c4362 : fffffa80`06f66610 fffffa80`06f66390 00000000`00000001 00000000`00000000 : nt!PipCallDriverAddDevice+0x19a
fffff880`03362950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x2b2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02ed5920 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

Followup: MachineOwner
---------