Windows 7 forum: Blue Screen 'minidump' crash - Windows 7

by: ericschultz02 January 22, 2010 2:09 PM PST

Like this

0 people like this thread

Staff pick

Blue Screen 'minidump' crash - Windows 7

by ericschultz02 - 1/22/10 2:09 PM

I have an HP Pavilion Slimline Running Dual Core E5200 @ 2.5 GHz.

For some reason I keep getting the "Blue Screen" and then the computer shuts down. I ran a crash detector and it gave me the following information but I can't seem to dig up any solutions to the probelm. Please Help.

Crash Detector Info:

On Fri 22/01/2010 8:49:32 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004FD7060, 0xFFFFF80000B9C518, 0xFFFFFA8006F97CA0)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\012210-36613-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Fri 22/01/2010 2:21:27 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80039DE040, 0xFFFFF800043DA740)
Error: Unknown
Dump file: C:\Windows\Minidump\012110-34351-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Thu 21/01/2010 7:01:42 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80039ED040, 0xFFFFF80000B9C510)
Error: Unknown
Dump file: C:\Windows\Minidump\012010-35318-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Thu 21/01/2010 4:05:20 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003A22B60, 0xFFFFF80000B9C510)
Error: Unknown
Dump file: C:\Windows\Minidump\012010-25443-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Thu 21/01/2010 1:31:05 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80039DFB60, 0xFFFFF80000B9C510)
Error: Unknown
Dump file: C:\Windows\Minidump\012010-32775-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Wed 20/01/2010 6:29:07 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8005E5F060, 0xFFFFF80000B9C518, 0xFFFFFA8006957C10)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\011910-30654-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.




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

6 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.

Thanks,

Frustrated Windows 7 User

Forum Icon Legend

  • UnreadUnread
  • ReadRead
  • Locked threadLocked thread
  •   
  •   
  •   
  •   
  •   
  •   
  •   
  • ModeratorModerator
  • CNET StaffCNET Staff
  • Samsung StaffSamsung Staff
  • Norton Authorized Support TeamNorton Authorized Support Team
  • AVG StaffAVG Staff
  • avast! Staffavast! Staff
  • Webroot Support TeamWebroot Support Team
  • Acer Customer Experience TeamAcer Customer Experience Team
  • Windows Outreach TeamWindows Outreach Team
  • DISH staffDISH staff
  • Dell StaffDell Staff
  • Intel StaffIntel Staff
  • QuestionQuestion
  • Resolved questionResolved question
  • General discussionGeneral discussion
  • TipTip
  • Alert or warningAlert or warning
  • PraisePraise
  • RantRant

You are e-mailing the following post: Post Subject

Your e-mail address is used only to let the recipient know who sent the e-mail and in case of transmission error. Neither your address nor the recipient's address will be used for any other purpose.

Sorry, there was a problem emailing this post. Please try again.

Submit Email Cancel

Thank you. Sent email to

Close

Thank you. Sent email to

Close

You are reporting the following post: Post Subject

If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.

Offensive: Sexually explicit or offensive language

Spam: Advertisements or commercial links

Disruptive posting: Flaming or offending other users

Illegal activities: Promote cracked software, or other illegal content

Sorry, there was a problem submitting your post. Please try again.

Submit Report Cancel

Your message has been submitted and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.

Close

Your message has been submitted and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.

Close

You are posting a reply to: Post Subject

The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to the CNET Forums policies for details. All submitted content is subject to CBS Interactive Site Terms of Use.

You are currently tracking this discussion. Click here to manage your tracked discussions.

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

Sorry, there was a problem submitting your post. Please try again.

Sorry, there was a problem generating the preview. Please try again.

Duplicate posts are not allowed in the forums. Please edit your post and submit again.

Submit Reply Preview Cancel

Thank you, , your post has been submitted and will appear on our site shortly.

Close