Blue Screen,kernel-power ID 41 help :(

aert · Nov 16, 2010

Hi.Two weeks ago i bought a new laptop :ASUS K52JB.I have installed windows 7 ultimate (x64).And so after two days a blue screen started to appear together with restart.I checked the eventviewer and I saw this message:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x000000000004200d, 0x0000000000000000, 0x5d979e4e1f4d9296). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111710-18252-01.
And after the restart a window appear that says
'The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.'
I did ram and hdd check and everything seems to be OK

memory.dmp

usasma · Nov 16, 2010

Please run this memory test to double check your memory: Memory Diagnostics (read the details at the link)

Please uninstall DaemonTools and/or Alcohol 120%, then use this free tool to remove the sptd.sys driver: DuplexSecure - FAQ - Remove 64 bit sptd.sys

It is possible that the following older drivers may be causing your problems.
Please either REMOVE or Update the older drivers listed below.

Code:
HOW TO FIND DRIVERS:
DO NOT use Windows Update or the Update Driver function of Device Manager as they are not the most current versions available.
Also, DO NOT update from the PC Manufacturer's website unless the Driver Reference cited below states that you should get the drivers from the OEM.

The most common drivers are located on this page: Driver Reference
If you can't find the driver, post back and we'll see what we can find.

Here's the older drivers that were found in the memory dump files:

Code:

[font=lucida console] sncduvc.SYS Mon Dec 29 04:14:26 2008 (495894F2) - Suyin USB 2.0 Webcam driver - [url=http://www.carrona.org/dvrref.html#sncduvc.SYS]Driver Reference[/url] ghaio.sys Mon May 30 05:34:05 2005 (429ADE0D) - ASUS NB Probe program - [url=http://www.carrona.org/dvrref.html#ghaio.sys]Driver Reference[/url] [/font]

More info about the STOP 0x4E error (shorthand for what you posted) is available here: BSOD Index
You also have STOP 0xD1 errors. More info on that error here: BSOD Index
Also STOP 0x1A, more info here: BSOD Index
Also STOP 0xA, more info here: BSOD Index
Also STOP 0x3B, more info here: BSOD Index
Also STOP 0xF5, more info here: BSOD Index
Also STOP 0x1E, more info here: BSOD Index

Most often a large number of different errors suggests a hardware problem (this one seems to point at memory). Running Driver Verifier may help us to narrow it down a bit. Please follow these instructions to run Driver Verifier:

Code:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 17:08:10.683 2010 (UTC - 5:00)
System Uptime: 0 days 3:37:55.870
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0004200d 00000000`00000000 5d979e4e`1f4d9296
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 13:29:40.793 2010 (UTC - 5:00)
System Uptime: 1 days 19:40:50.369
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3a2 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02b9180c 00000000`00000000 000010eb`baef57f7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 14 17:41:23.399 2010 (UTC - 5:00)
System Uptime: 0 days 0:54:48.586
BugCheck D1, {1, 2, 1, fffff88001aa5022}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments 00000000`00000001 00000000`00000002 00000000`00000001 fffff880`01aa5022
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 14 16:45:40.613 2010 (UTC - 5:00)
System Uptime: 0 days 1:11:04.800
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  UNS.exe
Bugcheck code 0000001A
Arguments 00000000`00041287 00007ff4`c7fd2803 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 11 13:02:53.793 2010 (UTC - 5:00)
System Uptime: 0 days 2:18:42.370
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 0000559a`01bc89f1 00000000`00000002 00000000`00000000 fffff800`02b38aef
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 11 07:43:05.901 2010 (UTC - 5:00)
System Uptime: 0 days 5:08:21.477
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02b65165 fffff880`05ddbca0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 14:19:52.441 2010 (UTC - 5:00)
System Uptime: 0 days 1:21:18.018
BugCheck F5, {68, fffff8a002b11010, fffff8a002b11060, 0}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamLogForNL+203 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF5
PROCESS_NAME:  svchost.exe
Bugcheck code 000000F5
Arguments 00000000`00000068 fffff8a0`02b11010 fffff8a0`02b11060 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

aert · Nov 17, 2010

Thanks for the quick reply.I am not sure about the memory ,I think its all about the HDD(write).There is a strange sound that comes out from my computer ,but this sound disappear when my pc is in sleep mode,that stirs me to think that there is a defect on the HDD.The sound isn't very loud and it sounds like mosquito' whiz.It could be the head of the hdd ?

usasma · Nov 17, 2010

Then try these free diagnostics for your hard drive: HD Diagnostic (read the details at the link)

aert · Nov 18, 2010

Ok i've tryed this HDD diagnostic program but it didn't work at all.It just did't load my drives(

http://www.hitachigst.com/hdd/support/download.htm#DFT )
I made a double check on the memory with memtest86 and there weren't any errors.

.Meanwhile I saw some new errors at the eventviewer.(this time my pc didn't restart but just stuck.

usasma · Nov 18, 2010

Try the Seagate Seatools test
Also try the error scan function in HDTune Pro

Each of the errors happened one time and one time only - at 2:45 pm today. What was happening with the computer at that time?

aert · Nov 19, 2010

Done.

usasma · Nov 19, 2010

There doesn't appear to be any issues with the hard drive.
Now we wait for any further BSOD's....

aert · Nov 19, 2010

ok BSOD

usasma · Nov 19, 2010

sptd.sys is still in the dump files. Please follow the instructions in my first post for removing it: DuplexSecure - FAQ

Additionally, the 2 outdated drivers that I mentioned haven't been removed or updated. Please either update or remove those drivers.

No memory test results, no Driver Verifier enabled memory dumps - both as I requested previously.

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 19 16:27:02.431 2010 (UTC - 5:00)
System Uptime: 0 days 6:11:30.007
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  uTorrent.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`01a9706c fffff880`08db38a0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 19 10:15:03.988 2010 (UTC - 5:00)
System Uptime: 0 days 20:35:30.549
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6368 )
BUGCHECK_STR:  0x1a_31
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000001A
Arguments 00000000`00000031 fffffa80`0a7e4260 fffff880`08390000 fffff8a0`0322b270
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

aert · Nov 20, 2010

Ok i have removed the sptd.sys.I made a double check on the RAM and everything is fine,but I still have crashes.

usasma · Nov 20, 2010

Please continue to post the crash dump files - and we'll continue to analyze them and make suggestions for things to do.

aert · Nov 22, 2010

Well yesterday my PC worked correctly for 15 hours then I put it in to hibernate mode .Today I've resumed the windows and it worked fine for 3 hours then it started to lag and it finally stuck....In the eventviewer there was a kernel power error but there wasn't any new file in the minidump folder....

Edit: ok stuck 3 times in a row when downloading torrent file (2,5gb)

P.S.:blue screen

usasma · Nov 22, 2010

In post #2 I asked you to update or remove these programs:

sncduvc.SYS Mon Dec 29 04:14:26 2008 (495894F2)
- Suyin USB 2.0 Webcam driver
- Driver Reference

ghaio.sys Mon May 30 05:34:05 2005 (429ADE0D)
- ASUS NB Probe program
- Driver ReferenceThey are still present in your memory dumps - and I wouldn't be surprised if the ghaio.sys file from 2005 is the cause of the problem.

Also, please run Driver Verifier according to these instructions:

Code:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 11:22:55.650 2010 (UTC - 5:00)
System Uptime: 0 days 1:11:31.211
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+2a2 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02ae2d18 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

aert · Nov 23, 2010

Well,the old drivers have been removed .Now we will wait

aert · Nov 24, 2010

Error

P.S. I have cleaned 64 registry errors (with uniblue registry booster)

usasma · Nov 24, 2010

Have you run Driver Verifier? Driver Verifier Settings
Have you run the memory test? Memory Diagnostics

Memory Management error in this BSOD:
BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 24 10:36:16.998 2010 (UTC - 5:00)
System Uptime: 1 days 2:23:54.559
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  plugin-contain
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`0781c001 00000000`00001b73 fffff700`01080000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

aert · Nov 24, 2010

I did a mem test ofc ...but i didn't run driver verifier ..i don't think that is software problem but a hardware ...

usasma · Nov 24, 2010

Your system, your choice.
Good luck!

aert · Nov 25, 2010

Well ,I have started the driver verifier and so far(2 hours) there aren't any errors.

Blue Screen,kernel-power ID 41 help :(

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer