System crash (BSOD) - ntoskrnl.exe?

[Hayorti]

A couple of months ago I started getting sporadic system crashes for reasons I didn't understand, so I simply reinstalled Windows and that solved my problem for a bit. A couple of weeks ago, I started having the same problem but I noticed the 0x1E stop code, I didn't know better at the time, so I just did another quick reinstall and that was fine till a couple of days ago, when lo and behold, I started getting system crashes again. This time, there were 0x1E stop codes and 0xD1 stop codes, with a line identifying sortport.sys as the reason for the crash. I'd realized that in Normal Mode, Windows would crash when I opened Google Chrome or when Gmail Notifier initialized (with Chrome as the default browser), so after uninstalling those, I no longer got the sortport.sys system crash. The 0x1E system crashes did continue, but I do get 0xD1 codes still, but WhoCrashed is telling me that ntoskrnl.exe is the reason for those crashes. I doubt it's a hardware problem because reinstalling Windows shouldn't affect the health of my hardware. Unless an update released 2 months ago is conflicting with one of my drivers or a piece of my hardware, and it just so happens to be installing itself (Via Windows Update) a short time after Windows has been installed.

Several other things to take into consideration:

My HDD is split into 2 partitions, the first is for system files, and the other is for user files. I always log in to my Standard user account, and I have to put in a password for any program that tries to alter system files (eliminating the need for a running antivirus).

In Safe Mode, the computer doesn't crash at all, which further convinces me that it's a software problem, because if it was a hardware issue the system would crash all the time.

In Safe Mode, if I started Google Chrome, it would crash due to a driver error (From my experience, it was either storport.sys or nvstor64.sys)

In Safe Mode, if I log in to my Administrator profile, the system crashes with either a 0x1E or 0xD1 sop code.

-----

Computer Specs.

OS: Windows 7 Home Premium x64
CPU: Intel Pentium Dual Core E5300
HDD: Seagate Barracuda Green 320GB HDD
RAM: 3GB DDR2 PC2-4200 - 533 MHz (2x1GB Kingston + 2x512MB Samsung)
GPU: MSI GTX460 1GB GDDR5 Cyclone
Sound: Creative Sound Blaster Audigy 2
Motherboard: XFX 750i Motherboard

 

[Maguscreed]

ntoskrnl.exe failures can point to a list of problems most of them related to corruption of one form or another. I was not aware this problem could even occur with win 7, I have seen it in win xp several times though. a secure file check or disc scan will usually point you to the culprit.

..anyhow I'm blabbering, the first thing I would do in your situation would be to run a registry scan with your preferred registry utility. Next step would be a secure file check, then a disc check.
Finally I would check the ram. Usually bad ram will lead to a variety of error messages though not a consistent one.

 

[DeanP]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Hayorti]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Just uploaded it

Unfortunately, the Performance Monitor results were giving me an error, so I couldn't see them, let alone save them. So I just uploaded the dumps.

 

[Hayorti]

ntoskrnl.exe failures can point to a list of problems most of them related to corruption of one form or another. I was not aware this problem could even occur with win 7, I have seen it in win xp several times though. a secure file check or disc scan will usually point you to the culprit.

..anyhow I'm blabbering, the first thing I would do in your situation would be to run a registry scan with your preferred registry utility. Next step would be a secure file check, then a disc check.
Finally I would check the ram. Usually bad ram will lead to a variety of error messages though not a consistent one.

I did run CCleaner's registry cleaner...and instead of getting a 0x1E stop code in normal mode, I got a 0xD1 code and it displayed a line about storport.sys again

 

[Maguscreed]

0xd1 = DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bad driver or device would be my guess.
If you are running any virtual devices like daemon tools, or alcohol 120% I would remove them for the time being.
Would follow that with hdd diagnostics.

..scratch that your sysinfo is so full of faulting applications / services I don't even know where to begin. I'll defer to one of the senior guys around here.

 

[DeanP]

If you are running any virtual devices like daemon tools, or alcohol 120% I would remove them for the time being.

The dump does not mention sptd.sys (Daemon Tools/Alcohol 120%)

You have old drivers to update, update them. They are notorious for BSOD.

SSPORT.sys Fri Aug 12 11:07:32 2005
Samsung Printing Driver
Samsung
If there is no update available - upgrade your printer to a Windows 7 Capability

nvstor64.sys Sat Oct 27 07:50:36 2007

nvmfdx64.sys Sun Nov 18 12:47:57 2007

dump_nvstor64.sys Sat Oct 27 07:50:36 2007

 

[Hayorti]

If you are running any virtual devices like daemon tools, or alcohol 120% I would remove them for the time being.

The dump does not mention sptd.sys (Daemon Tools/Alcohol 120%)

You have old drivers to update, update them. They are notorious for BSOD.

SSPORT.sys Fri Aug 12 11:07:32 2005
Samsung Printing Driver
Samsung
If there is no update available - upgrade your printer to a Windows 7 Capability

nvstor64.sys Sat Oct 27 07:50:36 2007

nvmfdx64.sys Sun Nov 18 12:47:57 2007

dump_nvstor64.sys Sat Oct 27 07:50:36 2007

What's the ebst way to update that driver?

 

[DeanP]

I will be on the computer sometime, I recommend that you do something about the Samsung driver first and I will take a look at others...

...

Sent from my iPad

 

[Hayorti]

I will be on the computer sometime, I recommend that you do something about the Samsung driver first and I will take a look at others...

...

Sent from my iPad

I completely uninstalled the Samsung driver, so that should no longer be a problem.

However, everytime I try to update the motherboard drivers, it asks to uninstall the existing storage drivers, but it crashes everytime it tries to access those drivers. It gives me another 0x1E stop code...(I attached a new archive of all the dump files).

Also, I tried running Seagate's SeaTools to scan my HDD, but everytime I try to run a "Long Test", I get strings of random characters on the screen that just go on for hours and hours. So I have no idea what's going on with that...

 

[Hayorti]

Okay, I put my hard drive into an enclosure I had, connected it to my laptop, and ran a full SeaTools HDD scan, and it passed, so I know that my hard drive isn't the issue.

 

[Hayorti]

Bump...Common guys, still need your help.

 

[zigzag3143]

A couple of months ago I started getting sporadic system crashes for reasons I didn't understand, so I simply reinstalled Windows and that solved my problem for a bit. A couple of weeks ago, I started having the same problem but I noticed the 0x1E stop code, I didn't know better at the time, so I just did another quick reinstall and that was fine till a couple of days ago, when lo and behold, I started getting system crashes again. This time, there were 0x1E stop codes and 0xD1 stop codes, with a line identifying sortport.sys as the reason for the crash. I'd realized that in Normal Mode, Windows would crash when I opened Google Chrome or when Gmail Notifier initialized (with Chrome as the default browser), so after uninstalling those, I no longer got the sortport.sys system crash. The 0x1E system crashes did continue, but I do get 0xD1 codes still, but WhoCrashed is telling me that ntoskrnl.exe is the reason for those crashes. I doubt it's a hardware problem because reinstalling Windows shouldn't affect the health of my hardware. Unless an update released 2 months ago is conflicting with one of my drivers or a piece of my hardware, and it just so happens to be installing itself (Via Windows Update) a short time after Windows has been installed.

Several other things to take into consideration:

My HDD is split into 2 partitions, the first is for system files, and the other is for user files. I always log in to my Standard user account, and I have to put in a password for any program that tries to alter system files (eliminating the need for a running antivirus).

In Safe Mode, the computer doesn't crash at all, which further convinces me that it's a software problem, because if it was a hardware issue the system would crash all the time.

In Safe Mode, if I started Google Chrome, it would crash due to a driver error (From my experience, it was either storport.sys or nvstor64.sys)

In Safe Mode, if I log in to my Administrator profile, the system crashes with either a 0x1E or 0xD1 sop code.

-----

Computer Specs.

OS: Windows 7 Home Premium x64
CPU: Intel Pentium Dual Core E5300
HDD: Seagate Barracuda Green 320GB HDD
RAM: 3GB DDR2 PC2-4200 - 533 MHz (2x1GB Kingston + 2x512MB Samsung)
GPU: MSI GTX460 1GB GDDR5 Cyclone
Sound: Creative Sound Blaster Audigy 2
Motherboard: XFX 750i Motherboard

Several Problems

1-Old drivers
Update at least these (one from 2005)

SSPORT.sys    8/11/2005 18:07:32    0x42fbda34    fffff880`02b9d000    fffff880`02ba5000        0x00008000                    
nvstor64.sys    10/26/2007 13:50:36    0x472236fc    fffff880`01161000    fffff880`01183000        0x00022000                    
dump_nvstor64.sys    10/26/2007 13:50:36    0x472236fc    fffff880`044c3000    fffff880`044e5000        0x00022000                    
nvmfdx64.sys    11/17/2007 18:47:57    0x473f7dad    fffff880`03e7c000    fffff880`03fe4c80        0x00168c80                    
spldr.sys    5/11/2009 11:56:27    0x4a0858bb    fffff880`018fb000    fffff880`01903000        0x00008000                    
amdxata.sys    5/19/2009 12:56:59    0x4a12f2eb    fffff880`01183000    fffff880`0118e000        0x0000b000                    
nvstor.sys    5/20/2009 1:45:37    0x4a13a711    fffff880`00dce000    fffff880`00df9000        0x0002b000

2-Your storage driver nvstor64.sys
Re-install as it was partially responsible in the most recent crash

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

3-Storport.sys a win 7 driver that needs to be repaired. Run a system file check to do that

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\012311-30359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02e9ee50
Debug session time: Sun Jan 23 00:44:44.515 2011 (GMT-5)
System Uptime: 0 days 0:01:30.000
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {69, 2, 0, fffff880011000ed}

Unable to load image \SystemRoot\system32\DRIVERS\nvstor64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvstor64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
Probably caused by : storport.sys ( storport!StorPortNotification+3d )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000069, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880011000ed, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f090e0
 0000000000000069 

CURRENT_IRQL:  2

FAULTING_IP: 
storport!StorPortNotification+3d
fffff880`011000ed 488b4268        mov     rax,qword ptr [rdx+68h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  dwm.exe

TRAP_FRAME:  fffff80000ba2b00 -- (.trap 0xfffff80000ba2b00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002300670 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011000ed rsp=fffff80000ba2c90 rbp=fffffa800168b218
 r8=fffff88002300670  r9=fffff80000ba2d20 r10=fffffa80016ae008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
storport!StorPortNotification+0x3d:
fffff880`011000ed 488b4268        mov     rax,qword ptr [rdx+68h] ds:e100:00000000`00000069=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd0ca9 to fffff80002cd1740

STACK_TEXT:  
fffff800`00ba29b8 fffff800`02cd0ca9 : 00000000`0000000a 00000000`00000069 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba29c0 fffff800`02ccf920 : fffffa80`0168a1b0 fffffa80`0168a1b0 00000000`00000002 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2b00 fffff880`011000ed : 00000000`00000000 fffffa80`0168b218 fffff800`00ba2d10 fffff880`011653ed : nt!KiPageFault+0x260
fffff800`00ba2c90 fffff880`011646c2 : 00000000`00000002 fffffa80`016ae008 fffff880`02300670 fffff800`00ba2d00 : storport!StorPortNotification+0x3d
fffff800`00ba2d10 00000000`00000002 : fffffa80`016ae008 fffff880`02300670 fffff800`00ba2d00 00000000`00000000 : nvstor64+0x36c2
fffff800`00ba2d18 fffffa80`016ae008 : fffff880`02300670 fffff800`00ba2d00 00000000`00000000 fffff880`0117270a : 0x2
fffff800`00ba2d20 fffff880`02300670 : fffff800`00ba2d00 00000000`00000000 fffff880`0117270a fffffa80`017b9380 : 0xfffffa80`016ae008
fffff800`00ba2d28 fffff800`00ba2d00 : 00000000`00000000 fffff880`0117270a fffffa80`017b9380 00000000`00000000 : 0xfffff880`02300670
fffff800`00ba2d30 00000000`00000000 : fffff880`0117270a fffffa80`017b9380 00000000`00000000 00000000`00000000 : 0xfffff800`00ba2d00


STACK_COMMAND:  kb

FOLLOWUP_IP: 
storport!StorPortNotification+3d
fffff880`011000ed 488b4268        mov     rax,qword ptr [rdx+68h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  storport!StorPortNotification+3d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: storport

IMAGE_NAME:  storport.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcace

FAILURE_BUCKET_ID:  X64_0xD1_storport!StorPortNotification+3d

BUCKET_ID:  X64_0xD1_storport!StorPortNotification+3d

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000069, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880011000ed, address which referenced memory

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


READ_ADDRESS:  0000000000000069 

CURRENT_IRQL:  2

FAULTING_IP: 
storport!StorPortNotification+3d
fffff880`011000ed 488b4268        mov     rax,qword ptr [rdx+68h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  dwm.exe

TRAP_FRAME:  fffff80000ba2b00 -- (.trap 0xfffff80000ba2b00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002300670 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011000ed rsp=fffff80000ba2c90 rbp=fffffa800168b218
 r8=fffff88002300670  r9=fffff80000ba2d20 r10=fffffa80016ae008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
storport!StorPortNotification+0x3d:
fffff880`011000ed 488b4268        mov     rax,qword ptr [rdx+68h] ds:e100:00000000`00000069=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd0ca9 to fffff80002cd1740

STACK_TEXT:  
fffff800`00ba29b8 fffff800`02cd0ca9 : 00000000`0000000a 00000000`00000069 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba29c0 fffff800`02ccf920 : fffffa80`0168a1b0 fffffa80`0168a1b0 00000000`00000002 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2b00 fffff880`011000ed : 00000000`00000000 fffffa80`0168b218 fffff800`00ba2d10 fffff880`011653ed : nt!KiPageFault+0x260
fffff800`00ba2c90 fffff880`011646c2 : 00000000`00000002 fffffa80`016ae008 fffff880`02300670 fffff800`00ba2d00 : storport!StorPortNotification+0x3d
fffff800`00ba2d10 00000000`00000002 : fffffa80`016ae008 fffff880`02300670 fffff800`00ba2d00 00000000`00000000 : nvstor64+0x36c2
fffff800`00ba2d18 fffffa80`016ae008 : fffff880`02300670 fffff800`00ba2d00 00000000`00000000 fffff880`0117270a : 0x2
fffff800`00ba2d20 fffff880`02300670 : fffff800`00ba2d00 00000000`00000000 fffff880`0117270a fffffa80`017b9380 : 0xfffffa80`016ae008
fffff800`00ba2d28 fffff800`00ba2d00 : 00000000`00000000 fffff880`0117270a fffffa80`017b9380 00000000`00000000 : 0xfffff880`02300670
fffff800`00ba2d30 00000000`00000000 : fffff880`0117270a fffffa80`017b9380 00000000`00000000 00000000`00000000 : 0xfffff800`00ba2d00


STACK_COMMAND:  kb

FOLLOWUP_IP: 
storport!StorPortNotification+3d
fffff880`011000ed 488b4268        mov     rax,qword ptr [rdx+68h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  storport!StorPortNotification+3d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: storport

IMAGE_NAME:  storport.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcace

FAILURE_BUCKET_ID:  X64_0xD1_storport!StorPortNotification+3d

BUCKET_ID:  X64_0xD1_storport!StorPortNotification+3d

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

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

 

[Hayorti]

I'll try running a System File Check, but like I'd said before, I can't update any of the nVidia Storage Drivers because every time the installer tries to uninstall the old one, the computer crashes again.

Thank you for your response, though.

 

[Maguscreed]

I'll try running a System File Check, but like I'd said before, I can't update any of the nVidia Storage Drivers because every time the installer tries to uninstall the old one, the computer crashes again.

Thank you for your response, though.

Have you tried performing this while in safe mode?

 

[Hayorti]

I'll try running a System File Check, but like I'd said before, I can't update any of the nVidia Storage Drivers because every time the installer tries to uninstall the old one, the computer crashes again.

Thank you for your response, though.

Have you tried performing this while in safe mode?

Well, I can only use my computer while in Safe Mode...
And I just ran a System File Check and Windows says that all my files are fine.
I can't run Windows Update either to update some of the other out of date system drivers...
I'm updating the ssport.sys driver, but that definitely won't solve my problem.

 

[Hayorti]

Last night, I managed to get into my user account in Normal Mode, and Windows Update started updating a couple of things. I had a chance to update ssport.sys manually, but I couldn't overwrite Windows Update's nVidia Storage drivers with the ones from the nVidia site...the system needed a restart after updating, and after that it just went back to normal.

The odd thing now is that when I log into safe mode, I can't see any of my desktop icons, Explorer won't recognize my external hard drive, and WhoCrashed can't seem to find the path for the dumps.

What do you guys think?

 

[ShaneBaesen]

Same issue

A couple of months ago I started getting sporadic system crashes for reasons I didn't understand, so I simply reinstalled Windows and that solved my problem for a bit. A couple of weeks ago, I started having the same problem but I noticed the 0x1E stop code, I didn't know better at the time, so I just did another quick reinstall and that was fine till a couple of days ago, when lo and behold, I started getting system crashes again. This time, there were 0x1E stop codes and 0xD1 stop codes, with a line identifying sortport.sys as the reason for the crash. I'd realized that in Normal Mode, Windows would crash when I opened Google Chrome or when Gmail Notifier initialized (with Chrome as the default browser), so after uninstalling those, I no longer got the sortport.sys system crash. The 0x1E system crashes did continue, but I do get 0xD1 codes still, but WhoCrashed is telling me that ntoskrnl.exe is the reason for those crashes. I doubt it's a hardware problem because reinstalling Windows shouldn't affect the health of my hardware. Unless an update released 2 months ago is conflicting with one of my drivers or a piece of my hardware, and it just so happens to be installing itself (Via Windows Update) a short time after Windows has been installed.

Several other things to take into consideration:

My HDD is split into 2 partitions, the first is for system files, and the other is for user files. I always log in to my Standard user account, and I have to put in a password for any program that tries to alter system files (eliminating the need for a running antivirus).

In Safe Mode, the computer doesn't crash at all, which further convinces me that it's a software problem, because if it was a hardware issue the system would crash all the time.

In Safe Mode, if I started Google Chrome, it would crash due to a driver error (From my experience, it was either storport.sys or nvstor64.sys)

In Safe Mode, if I log in to my Administrator profile, the system crashes with either a 0x1E or 0xD1 sop code.

-----

Computer Specs.

OS: Windows 7 Home Premium x64
CPU: Intel Pentium Dual Core E5300
HDD: Seagate Barracuda Green 320GB HDD
RAM: 3GB DDR2 PC2-4200 - 533 MHz (2x1GB Kingston + 2x512MB Samsung)
GPU: MSI GTX460 1GB GDDR5 Cyclone
Sound: Creative Sound Blaster Audigy 2
Motherboard: XFX 750i Motherboard

I am having the same issue, my HP PC is only 6 months old, and it continues to crash. I have it under warranty, and after having it sent off for a month, it ran fine for about a week, and it starts to crash again. It has been checked out by HP and the driver is not bad. It seems to me that windows 7 is a bad program and needs to be looked into further instead of blaming it on the hard drive. I bought the top of the line HP, and take extreme care of it. I am currently on my 3 year old PC typing this as once again my new computer restores. And by the way my old PC runs on vista with no problems!!

 

[DeanP]

It seems to me that windows 7 is a bad program

Windows 7 is not a bad OS. You have to update drivers in Vista and XP as well. Get used to it...
It's not that hard to update drivers.

 

[aggixx]

I am having the same issue, my HP PC is only 6 months old, and it continues to crash. I have it under warranty, and after having it sent off for a month, it ran fine for about a week, and it starts to crash again. It has been checked out by HP and the driver is not bad. It seems to me that windows 7 is a bad program and needs to be looked into further instead of blaming it on the hard drive. I bought the top of the line HP, and take extreme care of it. I am currently on my 3 year old PC typing this as once again my new computer restores. And by the way my old PC runs on vista with no problems!!

ntoskernel BSODs can be caused by many things, and most cases are different. I would suggest following the instructions in this thread that have already been given (update drivers etc.), and if that doesn't solve the problem, start a new thread with your problem and make sure to include that data from Blue Screen of Death (BSOD) Posting Instructions, as that will give much more information than your description of the problem likely ever will.