BSOD, computer won't wake, so confused


  1. fringe100
    Posts : 3
    Windows 7 Professional 64 bit
       New #1

    BSOD, computer won't wake, so confused


    OK I'm new here and not a computer expert so please bare with me! These forums are great by the way.

    I am running 64 bit OS Windows 7 Pro. Vista was originally installed and I downloaded this from my school so not sure whether 'full retail' or not. The computer is about 2 years old and I first installed about 8 mnths ago maybe and have not reinstalled since.

    The computer has recently gone crazy and would not wake up from sleep. I can here it running but the screen will not come up. I have to power off and back on and the next time it sleeps it will happen again. Tried setting monitor to never turn off and that worked at first then stopped. Computer started shutting down by itself and start up repair would run but not be able to fix anything then windows recovery would run, but the problem would remain. I was getting a Norton error so removed that thinking it was the problem, but that has not helped. Began getting blue screen / memory dump message. I am working in Safe Mode now as computer does not seem to be able to boot properly. The system would not generate the html file that is requested but I hope I have attached the other zip file correctly.

    Thanks for any help you can provide!

    Nikia
      My Computer
    Quote Quote

  3. usasma
    Posts : 5,705
    Win7 x64 + x86
       New #2

    There are problems with SPLDR in Device Manager. In most cases that I've seen, this is due to a malware infection. Please do this:
    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
    And, since you mention a Norton error, then please do this:
    Anti-Virus Removal:
    Please do the following:
    - download a free antivirus for testing purposes: Free AntiVirus
    - uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
    - remove any remnants of Norton using this free tool: KB Article Not Found
    - IMMEDIATELY install and update the free antivirus
    - check to see if this fixes the BSOD's
    Due to the number of different errors (this usually points at a hardware problem), please do this:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)
    If those diagnostics pass, then:
    - update all drivers from the System Manufacturer's website (even if you already have the latest version). Many of your drivers date from 2006.
    - visit Windows Update, get Service Pack 2, then get the remaining updates.

    BSOD BUGCHECK SUMMARY
    Code:
    
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6001.18427.x86fre.vistasp1_gdr.100218-0019
Debug session time: Tue Aug 31 13:58:45.375 2010 (UTC - 4:00)
System Uptime: 0 days 0:52:00.271
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
BugCheck 101, {61, 0, 803d1120, 1}
Probably caused by : ntkrpamp.exe
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Aug 31 08:59:30.957 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:30.582
BugCheck 7F, {8, 80050031, 6f8, fffff800dfe896c0}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  WMIADAP.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Mon Aug 30 16:49:14.011 2010 (UTC - 4:00)
System Uptime: 0 days 0:33:35.796
BugCheck D1, {7aa14, 2, 8, 7aa14}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2ac )
PROCESS_NAME:  Idle
BUGCHECK_STR:  0xD1
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Mon Aug 30 16:15:05.575 2010 (UTC - 4:00)
System Uptime: 0 days 0:20:01.520
BugCheck 101, {61, 0, 8ba97120, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
PROCESS_NAME:  Idle
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Debug session time: Mon Aug 30 15:54:28.485 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:06.377
BugCheck 101, {61, 0, 8ba97120, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
PROCESS_NAME:  Idle
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 23 22:44:38.193 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:16.972
BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 15:52:41.286 2010 (UTC - 4:00)
System Uptime: 0 days 2:29:39.066
BugCheck 50, {fffff900c232bb50, 0, fffff80002bc28fe, 0}
Probably caused by : win32k.sys ( win32k!NtUserSystemParametersInfo+264 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  LogonUI.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 12:48:29.061 2010 (UTC - 4:00)
System Uptime: 0 days 0:39:33.840
BugCheck A, {fffff8000a4fe70b, 2, 0, fffff80002ad9104}
Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+2d4 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  ccsvchst.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 12:08:04.127 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:12.906
BugCheck A, {fffffffffdb00300, 2, 1, fffff80002a9d357}
Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+527 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  ccsvchst.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 11:54:38.865 2010 (UTC - 4:00)
System Uptime: 0 days 3:18:28.644
BugCheck 3B, {c0000005, fffff80002ab7ec0, fffff880085f3160, 0}
Probably caused by : ntkrnlmp.exe ( nt!NtFreeVirtualMemory+3b0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ccsvchst.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 21 21:36:59.452 2010 (UTC - 4:00)
System Uptime: 0 days 6:11:35.231
BugCheck 7F, {8, 80050031, 6f8, fffff80002a94926}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 21 15:24:13.144 2010 (UTC - 4:00)
System Uptime: 0 days 0:28:21.799
BugCheck 101, {61, 0, fffff880009ea180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 21:20:01.084 2010 (UTC - 4:00)
System Uptime: 0 days 11:07:18.863
BugCheck D1, {0, 2, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  System
BUGCHECK_STR:  0xD1
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 15 15:01:08.887 2010 (UTC - 4:00)
System Uptime: 1 days 10:52:39.160
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for nvm62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvm62x64.sys
Probably caused by : nvm62x64.sys ( nvm62x64+252a0 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  uTorrent.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 04:03:34.199 2010 (UTC - 4:00)
System Uptime: 3 days 6:30:12.869
BugCheck 7F, {8, 80050031, 6f8, fffff80002ad5590}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May  3 23:23:21.357 2010 (UTC - 4:00)
System Uptime: 4 days 20:06:45.650
*** ERROR: Module load completed but symbols could not be loaded for fastfat.SYS
BugCheck 23, {e0107, fffff880050ed438, fffff880050ecca0, fffff88007795319}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
Probably caused by : fastfat.SYS ( fastfat+b319 )
PROCESS_NAME:  WINWORD.EXE
BUGCHECK_STR:  0x23
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer
    Quote Quote

  4. usasma
    Posts : 5,705
    Win7 x64 + x86
       New #3

    I just noticed that there are Vista and Win7 memory dumps (Vista occurred around 30 Aug).
    Have you reinstalled Vista, then reinstalled Win7?
      My Computer
    Quote Quote

  6. fringe100
    Posts : 3
    Windows 7 Professional 64 bit
    Thread Starter
       New #4

    Hi usasma,

    Thank you so much for your responses and taking the time to look at this. I apologize for my late reply, but I actually had a friend offer to look at the computer and due to my impatience with myself I took the easy way out and let him so he still has it in his possession now. What he's told me so far is that he believes it to be a memory issue and that there also seemed to be a problem with the antivirus. I had already uninstalled Norton using the removal tool as you advised and installed Avira, but according to him the installation had some errors.... He offered to install another antivirus program the name of which escapes me now. I'm going to forward the information you gave me to him as I know it would be helpful. When I get the computer back I want to update the drivers as you suggested. I understand that I need to install Service Pack 2 and this is going to sound like the dumbest question ever, but when you say to update from the manufacturer's website for all the drivers am I just going through Device Manager and updating all those drivers that way? I apologize I am really just trying to get the hang of all this. I'm also not sure about those Vista errors - I'm almost positive that I had reinstalled Vista prior to installing 7, but that was probably about a year ago I'm guessing.

    Thanks again for all your help and your patience with me.
      My Computer
    Quote Quote

  7. usasma
    Posts : 5,705
    Win7 x64 + x86
       New #5

    Not a problem. Don't update through Device Manager - that will update using the Windows Update website, and those drivers aren't always the newest or most compatible.

    If Win7 is installed, don't do anything unless you get another BSOD. The Win7 drivers are updated.
    If Vista is installed, visit the HP support website here: HPо - Laptops, Desktop, Printers, Servers, and more and download all the drivers for your model and OS.
      My Computer
    Quote Quote

  8. fringe100
    Posts : 3
    Windows 7 Professional 64 bit
    Thread Starter
       New #6

    Understood - thank u again!
      My Computer
    Quote Quote

 

  Related Discussions
Occasional BSOD On Computer Wake-up
in BSOD Help and Support

I recently put together a new computer about a month ago. Everything is running great except for one strange problem. I usually keep my computer on sleep mode overnight and on average about once every week I get a BSOD about 10 seconds after I wake my computer up. I've verified my memory using...
Hello, I have a new Dell laptop with Win7 Enterprise which BSOD's every once in a while when I hit the power button. I previously changed the power button to Hibernate. It does not always BSOD every single time. It sometimes BSODs when going to, and sometimes when waking up from Hibernate. ...
BSOD - New computer so confused :(
in BSOD Help and Support

Ok, this might take a while so bare with me. I bought a new computer (pieced it out) off of newegg. When everything came in I hooked everything up and tried to boot it up, it kept turning off and on over and over again. tried reseating everything, and noticed i had a bent pin on the mobo.. thought...
BSOD Every time I wake the computer
in BSOD Help and Support

I have had this problem with my Dell Laptop starting 6 months after purchase. They have replaced the harddrive twice, the memory and the monitor. I'm pretty sure it is a driver or Windows 7 update issue. The computer worked fine until I tried to update drivers, but also updated windows on the...
BSOD on computer wake, Local ID 1033
in BSOD Help and Support

Hello everyone! My computer crashed (BSOD) on my a couple of weeks ago. I have not been able to reproduce it. I believe it happened upon waking the computer. The system is less than a year old. Would like to know if its a software/driver issue or a hardware issue. Driving me nuts. For...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 й Designer Media Ltd
All times are GMT -5. The time now is 12:37.
Find Us