NTOSKRNL.EXE constant crashes

[TheOven]

NTOSKRNL.EXE constant crashes BSOD

Posting this from my old win xp system so please bear with me.

Got the bluescreen with ntoskrnl.exe listed.

Can not load win7 in normal mode.

Will load in safe mode but crashes when I try and launch anything, also crashes after ruining for a few min.

It is difficult to get information off the win7 system, even right clicking my computer crashes the system.

Managed to get the crash dumps copied.

I created a folder called minidump on the xp system, copied a crash dump from the win7 system into it and ran BSOD Dump & System File Collection app.

I am unable to run a system health report.

I removed the video card and tried using the on-board video but it did not resolve the crash.

I removed all but 1 stick of ram and tried it in all slots, also with other stick, but it did not resolve the crash.

I loaded the bios and applied fail safe defaults but it did not resolve the crash.

It is the 64bit version of win7

The ram, motherboard, and processor are about a year old. All other system components are 3+ years old.

I have zipped the first and most recent crashdump files as well as the output of the BSOD Dump & System File Collection app in separate files.

If anyone can help me with this I would be grateful.

If there is any other information I can supply I will try my best to do so.


Thank you for your time

 

[zigzag3143]

Posting this from my old win xp system so please bear with me.

Got the bluescreen with ntoskrnl.exe listed.

Can not load win7 in normal mode.

Will load in safe mode but crashes when I try and launch anything, also crashes after ruining for a few min.

It is difficult to get information off the win7 system, even right clicking my computer crashes the system.

Managed to get the crash dumps copied.

I created a folder called minidump on the xp system, copied a crash dump from the win7 system into it and ran BSOD Dump & System File Collection app.

I am unable to run a system health report.

I removed the video card and tried using the on-board video but it did not resolve the crash.

I removed all but 1 stick of ram and tried it in all slots, also with other stick, but it did not resolve the crash.

I loaded the bios and applied fail safe defaults but it did not resolve the crash.

It is the 64bit version of win7

The ram, motherboard, and processor are about a year old. All other system components are 3+ years old.

I have zipped the first and most recent crashdump files as well as the output of the BSOD Dump & System File Collection app in separate files.

If anyone can help me with this I would be grateful.

If there is any other information I can supply I will try my best to do so.


Thank you for your time

Several problems. Obviously you didnt do a clean win 7 install. Bios64.sys is from 2003 and could use some serious updating.


Sptd.sys a known cause of BSOD's. remove and replace

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.


5 copies of the Wsaudio.sys driver remove all but one.


Then I would run a system file check

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

BIOS64.sys    6/7/2003 8:12:00 PM        fffff880`03bd8000    fffff880`03be0000    0x00008000    0x3ee27f50                        
sptd.sys    10/11/2009 4:55:14 PM        fffff880`00e66000    fffff880`00f8c000    0x00126000    0x4ad24632                        
WsAudio_DeviceS(1).sys    7/23/2009 8:04:10 AM        fffff880`03c00000    fffff880`03c0b000    0x0000b000    0x4a6851ba                        
WsAudio_DeviceS(2).sys    7/23/2009 8:04:10 AM        fffff880`03cad000    fffff880`03cb8000    0x0000b000    0x4a6851ba                        
WsAudio_DeviceS(3).sys    7/23/2009 8:04:10 AM        fffff880`03cb8000    fffff880`03cc3000    0x0000b000    0x4a6851ba                        
WsAudio_DeviceS(4).sys    7/23/2009 8:04:10 AM        fffff880`03cc3000    fffff880`03cce000    0x0000b000    0x4a6851ba                        
WsAudio_DeviceS(5).sys    7/23/2009 8:04:10 AM        fffff880`03cce000    fffff880`03cd9000    0x0000b000    0x4a6851ba

 

[TheOven]

Thank you for the reply

I deleted Bios64.sys

I ran the sptd uninstaller and it said that no version was installed

I found the driver manually and deleted it.

I can not uninstall dtools, the system bsod as soon as I hit the uninstall


I deleted all but 1 copy of Wsaudio.sys

I ran system file check and it came back with no errors

I ran windows memory diagnostic and it had no errors

None of it fixed the problem


I can only load in safe mode and the system crashes if I try to do anything, control panel with not load without a bsod

I have attached the 2 latest crash reports

Sptd.sys a known cause of BSOD's. remove and replace

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.


5 copies of the Wsaudio.sys driver remove all but one.


Then I would run a system file check

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

BIOS64.sys    6/7/2003 8:12:00 PM        fffff880`03bd8000    fffff880`03be0000    0x00008000    0x3ee27f50                        
sptd.sys    10/11/2009 4:55:14 PM        fffff880`00e66000    fffff880`00f8c000    0x00126000    0x4ad24632                        
WsAudio_DeviceS(1).sys    7/23/2009 8:04:10 AM        fffff880`03c00000    fffff880`03c0b000    0x0000b000    0x4a6851ba                        
WsAudio_DeviceS(2).sys    7/23/2009 8:04:10 AM        fffff880`03cad000    fffff880`03cb8000    0x0000b000    0x4a6851ba                        
WsAudio_DeviceS(3).sys    7/23/2009 8:04:10 AM        fffff880`03cb8000    fffff880`03cc3000    0x0000b000    0x4a6851ba                        
WsAudio_DeviceS(4).sys    7/23/2009 8:04:10 AM        fffff880`03cc3000    fffff880`03cce000    0x0000b000    0x4a6851ba                        
WsAudio_DeviceS(5).sys    7/23/2009 8:04:10 AM        fffff880`03cce000    fffff880`03cd9000    0x0000b000    0x4a6851ba

 

[TheOven]

Not really sure what else to try other then a reformat/install.

Is there any way from looking at the crash reports to determine if it is not hardware related?

 

[TheOven]

so is that it then?

remove some drivers that weren't doing anything?

there isn't any information in those crash dumps that can narrow anything else down?

 

[zigzag3143]

Not really sure what else to try other then a reformat/install.

Is there any way from looking at the crash reports to determine if it is not hardware related?

The 2 newest were memory exceptions. The built in windows diagnostic doesnt stress RAM enough. Lets try running these



1-Memtest. Download 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.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



2-Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.