Beat way to test root cause of BSOD?

I just traded my17x R2 for the X7200 in my sign. I haven't yet done the upgrades listed such as RAM and Killer 1103. Currently the system has 10GB RAM (2x4GB + 1x2GB) and the Intel N6300.

I've installed a lot of apps and drivers but am getting a plethora is BSODs and looking at the dump files with BlueScreenViewer, each points to differ ant drivers.

I took my second Intel SSD and am going to do a fresh install. My question is what is the best process to go about testing? Should I start with a memory test and the cut stress test at a bare Win 7 install? Then stress test after each application install or each driver install?

What tools should I use to test? Trying to get a the system reliable. Seems like if I leave it on overnight or 24hrs, when I get back I have a system shutdown message due to a bsod or crash. Any suggestions s are welcome. Thanks!


Sent from my Samsung Captivate/ICS CM9 via Tapatalk.

 

download who crashed in my signature below. you will also find temp monitors and memtest for ram.

 

Thanks,

I have done a fresh install. Loaded no drivers or anything else and still getting BSOD's. Only think is Win 7 Pro, not even activated. Here is what WhoCrashed says.

Spoiler

System Information (local)
--------------------------------------------------------------------------------

computer name: XXXX-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 10728222720 total
VM: 2147352576, free: 1984143360



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 10/10/2012 9:39:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101012-10623-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0xCB99)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF80002EB723F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 10/10/2012 9:18:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101012-11138-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031BA83D, 0xFFFFF8800210BB50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 10/10/2012 8:44:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101012-9906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

I think I may remove all the memory modules and see how that works out. I think it may be pointing to memory. Last BSOD on Who Crashed was when I was trying to get NBR to load so I could type this post

 

OK I think it was bad memory. I have installed the nvidia drivers that came out today, and the newest Intel drivers for the N6300. I also removed all the memory and just installed a single 4GB stick.

Since swapping the memory, I was able to run an hour of OCCT and a full run of Intel burn test. So far no crashes. Before hand it would crash and BSOD after less then 5 min. I'm going to be replacing the RAM with three 8GB sticks. Hopefully no errors.

I had installed the stock RAM the previous user had in it. 1x4GB and 1x2GB. I also tried my 1333mhz CL7 2x2GB RAM and that didn't work either. I tried a single 4GB G.Skill stick and that worked. My other G.Skill stick is dead. Won't boot. Is it possible I have that much bad RAM?

Maybe the system and 980x just doesn't like the hyper-x RAM?



Sent from my Samsung Captivate/ICS CM9 via Tapatalk.

 

Have you tried varying the slot the one good 4 GIG stick is in to narrow it down to bad slot(s) possibly?
From what you said in Off Topic (not I am not cyber stalking you ) It could be a motherboard issue

 

Thats one thing I'll need to try. The most frustrating part is that any BSOD doesn't reference the same thing. They all seem differant.

But as for using a USB, Like I was saying in OT, Acronis won't finish the reimaging, it freezes, and the CAPs lock and Scroll Lock start flashing.

I've tried using a USB drive to boot Ubuntu to do a secure erase on the SSDs, and that was met with "Kernal Panic" errors, failed to boot, and also displayed flashing Caps lock and scroll lock. Num-lock isn't on at all. Havn't found anything online refering to what it may be. Right now it seems like it could be motherboard, CPU or GPU if it's hardware related.

 

Well that could be simply due to what was stored in the faulty memory at that time.

 

Good point. Man, feel like I'm going through tons of RAM. I'll try and move each module to each slot and see if it still persists. I think I have like 6 RAM modules sitting on the desk

 

Any luck champ!

Cheers.