Tech Support Forum banner
Cancel

BSOD on new install of Win7 64 bit

2483 Views 12 Replies 2 Participants Last post by  usasma, 
S
Hello, I have recently upgraded to 7 from Vista 64bit and have been having a lot of BSODs. There is no pattern that I can figure out when it crashes. Once I was just on the internet with Firefox running, another during Windows Update(latest two BSOD attempting to update KB954430 & KB982670), another while burning a DVD, and a few at system idle. My configuration consists of:

Windows 7 64bit full retail version
No original OS, custom built
Hardware is 1.5 years old
OS was installed on 07/12
Processor - AMD Phenom 9850 quad core
Video - NVIDIA GeForce 8600GT
Motherboard - ASUS M3A78 Pro
Power Supply - Antec BP500U 500 watt

I have attached the required files also.

I very much appreciate any help that can be given, thanks.

Attachments

Save
Like
Status
Not open for further replies.
1 - 13 of 13 Posts
S
I have had a 8 more since my post this morning. I am attaching the mini dump files.

I also forgot to mention above that I have ran memtest86+ on all my chips and they are fine.

Attachments

Save
Like
usasma
18 memory dumps
10 different STOP errors, blaming 10 different causes.
I strongly suspect a hardware issue

Please run these free diagnostics:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
http://www.carrona.org/hddiag.html (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: http://www.carrona.org/malware.html (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:
FurMark download site: http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Click to expand...
Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
Click to expand...
Click to expand...

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those 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.
Click to expand...
- - The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://www.carrona.org/dvrref.html ).
Please pay particular attention to any dated 2008 or earlier:
Code: 
[COLOR=Red]ASACPI.sys   Mon Oct 30 22:09:12 2006 - Asus ATK0110 ACPI Utility (a known BSOD maker)[/COLOR] - http://www.carrona.org/dvrref.html#ASACPI.sys
johci.sys    Thu Oct 09 02:43:47 2008 - JMicron OHCI Compliant IEEE 1394 Host Controller Driver - http://www.carrona.org/dvrref.html#johci.sys
RTSTOR64.SYS Thu Nov 13 03:47:04 2008 - Realtek Card reader - http://www.carrona.org/dvrref.html#RTSTOR64.SYS
SiRemFil.sys Wed Jun 20 15:42:10 2007 - Silicon Image driver - http://www.carrona.org/dvrref.html#SiRemFil.sys
SiWinAcc.sys Thu Jun 14 20:02:02 2007 - Silicon Image driver - comes with package for the SIxxxx drivers - http://www.carrona.org/dvrref.html#SiWinAcc.sys
BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 17 13:08:05.793 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:37.790
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : tcpip.sys ( tcpip+70996 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 17 12:56:39.943 2010 (UTC - 4:00)
System Uptime: 0 days 0:32:09.582
BugCheck 1000007E, {ffffffffc0000005, fffff88013e2e400, fffff88004df0648, fffff88004defeb0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+b0 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 17 12:18:28.481 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:24.120
BugCheck 24, {1904fb, fffff88006690bf8, fffff88006690460, fffff80002a8b672}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )
PROCESS_NAME:  McShield.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 17 11:29:12.362 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:35.375
BugCheck 3B, {c0000096, fffff80002acdb73, fffff880086da600, 0}
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXSave+70 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mDNSResponder.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 17 11:05:23.794 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:02.433
BugCheck 1000007E, {ffffffffc0000005, fffff80002e1fadb, fffff880031cb618, fffff880031cae80}
Probably caused by : memory_corruption ( nt!MmEnumerateAndReferenceImages+fb )
PROCESS_NAME:  ACService.exe
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 17 11:02:09.435 2010 (UTC - 4:00)
System Uptime: 0 days 1:24:54.073
BugCheck 19, {22, 0, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : tcpip.sys ( tcpip+7c8a3 )
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 17 09:36:25.912 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:15.925
BugCheck A, {6420000, 2, 1, fffff80002a8d4ff}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+9f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  msiexec.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 17 09:31:18.874 2010 (UTC - 4:00)
System Uptime: 0 days 10:20:06.513
BugCheck 3B, {c0000005, fffff80002af0b06, fffff8800807fe60, 0}
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+26 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  RapportLaunSer
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Fri Jul 16 23:09:34.420 2010 (UTC - 4:00)
System Uptime: 0 days 0:32:25.059
BugCheck 1A, {8886, fffffa8004170db0, fffffa8004158000, 605}
Probably caused by : win32k.sys ( win32k!sfac_ReadGlyphHeader+d0 )
BUGCHECK_STR:  0x1a_8886
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Fri Jul 16 22:36:20.530 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:16.153
BugCheck D1, {fffffad408028d58, 2, 1, fffff8800400d676}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+de )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Fri Jul 16 18:44:54.719 2010 (UTC - 4:00)
System Uptime: 0 days 2:44:47.342
BugCheck 3B, {c0000005, fffff80002880996, fffff880081b2130, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueue+9e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Fri Jul 16 13:01:49.573 2010 (UTC - 4:00)
System Uptime: 0 days 13:14:41.586
BugCheck 19, {3, fffff80002a09d10, fffff80002a09d10, fffff80000009d00}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Thu Jul 15 22:07:12.218 2010 (UTC - 4:00)
System Uptime: 0 days 0:50:50.215
BugCheck 1, {776ffbda, 0, ffff, fffff8800a046ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  RapportService
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Thu Jul 15 21:15:18.219 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:32.232
BugCheck D1, {fffff88079fba93a, a, 8, fffff88079fba93a}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_InterruptService+56 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Thu Jul 15 20:52:11.594 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:48.607
BugCheck 1000007E, {ffffffffc0000005, fffff800029875fc, fffff88003316608, fffff88003315e70}
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Thu Jul 15 20:42:50.929 2010 (UTC - 4:00)
System Uptime: 0 days 5:17:27.942
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 6, fffffa80083f7000}
Probably caused by : usbhub.sys ( usbhub+17fa )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Wed Jul 14 12:25:07.294 2010 (UTC - 4:00)
System Uptime: 0 days 0:26:45.933
BugCheck BE, {fffff88001659c30, 3870121, fffff88002f1a4c0, a}
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
Probably caused by : ndis.sys ( ndis+1fe7 )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Wed Jul 14 11:57:29.600 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:59.613
BugCheck A, {fffff88003317000, c, 1, fffff80002878701}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
See less See more
Save
Like
S
Thank you very much, I will let you know how it works out.
Save
Like
S
I have done everything suggested (which all passed) up to the point of installing new drivers. I have been searching, but cannot find a few:

johci.sys Thu Oct 09 02:43:47 2008 - JMicron OHCI Compliant IEEE 1394 Host Controller Driver - http://www.carrona.org/dvrref.html#johci.sys

SiRemFil.sys Wed Jun 20 15:42:10 2007 - Silicon Image driver - http://www.carrona.org/dvrref.html#SiRemFil.sys

SiWinAcc.sys Thu Jun 14 20:02:02 2007 - Silicon Image driver - comes with package for the SIxxxx drivers - http://www.carrona.org/dvrref.html#SiWinAcc.sys

I have installed the other drivers and it seems to not crash as much, but it still does. If you could point me in the right direction for the above drivers. Thank you very much!
Save
Like
S
Also, attached are the latest mini dump files since the updates.

Attachments

Save
Like
usasma
Let's not worry about those drivers right now (messing with them will get us off track). If you'd like to update them when we're done, post back and I'll give you some instructions on how to find out exactly which device that they belong to.

Please rename the C:\Windows\System32\drivers\johci.sys driver to johci.BAK and reboot (I'm not as sure about this one as I am the other 2).


Please check your hardware and software for compatibility at this link: http://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspx (compatibility problems can manifest as hardware problems in error reports).

Check for BIOS updates for your motherboard. The reason that I mention is this is my son's M4 series board had an issue with nVidia 8800 cards that would cause BSOD's.

I'm wondering about your McAfee security software. Please do this:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: http://www.carrona.org/freeav.html
- uninstall the McAfee from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of McAfee using this free tool:
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
Click to expand...
The rest of the memory dumps still suggest a hardware problem.
But, let's run Driver Verifier to be sure:
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: http://support.microsoft.com/?kbid=244617&sd=RMVP
Click to expand...
FYI - if Driver Verifier points to different errors - or to a bunch of Windows errors - then this will serve to confirm a hardware problem.

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Wed Jul 21 11:54:19.679 2010 (UTC - 4:00)
System Uptime: 0 days 1:12:06.317
BugCheck D1, {249c8b57, 2, 0, fffff8800167bb03}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : tcpip.sys ( tcpip+79b03 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  AdobeUpdater.e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Wed Jul 21 10:40:58.924 2010 (UTC - 4:00)
System Uptime: 0 days 0:24:30.563
BugCheck 3B, {c0000005, fffff960000f2c0f, fffff88003a190d0, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+73 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Wed Jul 21 10:14:48.809 2010 (UTC - 4:00)
System Uptime: 0 days 12:13:36.823
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck 1000007E, {ffffffffc000001d, fffff88000005807, fffff8800393b978, fffff8800393b1e0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+a133f )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Tue Jul 20 22:00:24.934 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:16.572
BugCheck D1, {e0d7c989, 2, 1, fffff88013e0c9dd}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( dxgmms1!VidSchUnwaitFlipQueue+115 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Tue Jul 20 21:37:18.927 2010 (UTC - 4:00)
System Uptime: 0 days 1:05:05.566
BugCheck 19, {20, fffffa80083fc950, fffffa80083fc9e0, 4090004}
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for mfeapfk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfeapfk.sys
Probably caused by : mfehidk.sys ( mfehidk+3afd2 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  wmplayer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Tue Jul 20 20:31:24.030 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:49.669
BugCheck 1A, {41284, b4b1001, 0, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a93 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Tue Jul 20 20:23:45.324 2010 (UTC - 4:00)
System Uptime: 0 days 0:21:11.337
BugCheck 34, {748, ffffffffc0000420, 0, 0}
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
Probably caused by : mfehidk.sys ( mfehidk+3546d )
BUGCHECK_STR:  0x34
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Tue Jul 20 19:44:30.721 2010 (UTC - 4:00)
System Uptime: 0 days 0:24:57.735
BugCheck D1, {fffffa9008de4728, 2, 0, fffff88004142378}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSelectContextFromThisPriority+30 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Tue Jul 20 19:18:44.612 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:52.625
BugCheck 3B, {c0000005, fffff88014cd8ea0, fffff88006944850, 0}
Probably caused by : hardware ( dxgkrnl!DXGDEVICE_NotifyAllContextsAboutNewDirectory+4 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Tue Jul 20 06:42:48.257 2010 (UTC - 4:00)
System Uptime: 0 days 9:10:17.271
BugCheck A, {1745c7b33f2c, 2, 1, fffff80002d16c22}
Probably caused by : ntkrnlmp.exe ( nt!RtlInterlockedClearBitRunEx+b2 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Mon Jul 19 21:31:15.869 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:51.882
BugCheck FC, {fffff880078e5370, 800000021f042963, fffff88008dc77b0, 2}
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
Probably caused by : hardware ( secdrv+370 )
BUGCHECK_STR:  0xFC
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Mon Jul 19 21:06:46.248 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:40.887
BugCheck D1, {fffffa7f91e91374, 6, 0, fffff880040fef2a}
Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+a )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Mon Jul 19 13:47:50.537 2010 (UTC - 4:00)
System Uptime: 0 days 17:12:59.550
BugCheck D1, {fffffa80557bcde0, 2, 0, fffff880041c3f1b}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiDecrementContextReference+b )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
See less See more
Save
Like
S
Alright, I did the Windows 7 compatibility check which showed everything passed.

Renamed johci.sys to johci.BAK

When I first had problems with Windows, the BIOS was the first thing I updated, so it is current.

I deleted McAfee and installed Avira AntiVirus.

I then enabled Driver Verifier. After rebooting I didn't even make it into Windows before crashing. I let it crash a couple times then booted into Safe Mode. I have attached the dump files.

Thanks again for all the help, I really appreciate it.

Attachments

Save
Like
usasma
Only 2 of the minidumps had any useable information.
And only one was a Driver Verifier Enabled Minidump

That one blamed RapportPG64.sys - which appears to be a component from here: http://www.trusteer.com/enterprise-deployment (a security application that's supposed to protect your banking info).

This link says it's causing BSOD's also: http://blog.mpecsinc.ca/2010/03/windows-7-bsods-rapportpg64sys-is.html

So, it's most likely that application that's causing your problems. BUT, make sure that there isn't any malware on your system BEFORE removing it. If malware is present, it may be causing RapportPG64.sys to crash in hopes of getting at your information.

In short, you've gotta remove the RapportPG64.sys program in order to fix the BSOD.
But, you want to be sure that nothing will steal your info.

Good luck!

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Thu Jul 22 19:54:06.336 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:25.381
BugCheck C9, {226, fffff88001455088, fffff9800aaaeee0, 0}
*** WARNING: Unable to verify timestamp for RapportPG64.sys
*** ERROR: Module load completed but symbols could not be loaded for RapportPG64.sys
Probably caused by : RapportPG64.sys ( RapportPG64+3088 )
BUGCHECK_STR:  0xc9_226
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  RapportMgmtSer
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Thu Jul 22 18:58:28.680 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:01.319
BugCheck 50, {62bd530, 0, 7fef8ab15c3, 8}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
See less See more
Save
Like
S
I removed the Rapport which has helped a lot with the blue screens. After that I reenabled driver verifier, which crashed twice on startup but then started up to Windows on the third time and ran fine. Attached are the latest dumps. Thanks!

Attachments

Save
Like
usasma
3 verifier enabled memory dumps this time - all pointing to Windows components.
This is most likely a hardware problem - but can also be a Windows issue.

Try running this program to see if it finds anything (I suspect that it won't, but we have to give it a try):
SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.
Click to expand...
While waiting for a reply, you can run these free diagnostics:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
http://www.carrona.org/memdiag.html (read the details at the link)
http://www.carrona.org/hddiag.html (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: http://www.carrona.org/malware.html (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:
FurMark download site: http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Click to expand...
Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
Click to expand...
Click to expand...
Don't want to forget about the Silicon Image drivers - so this is just a placeholder :0)

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Mon Jul 26 12:03:56.614 2010 (UTC - 4:00)
System Uptime: 0 days 13:03:19.627
BugCheck D1, {22, 2, 1, fffff88005ab4f2a}
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+90f2a )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sun Jul 25 22:59:29.591 2010 (UTC - 4:00)
System Uptime: 0 days 0:17:17.620
BugCheck A, {fffff800075f3108, 2, 0, fffff80002c7c418}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+338 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sun Jul 25 22:41:01.539 2010 (UTC - 4:00)
System Uptime: 0 days 12:18:53.583
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88013f764c3, fffff88003d514f8, fffff88003d50d60}
Probably caused by : nvlddmkm.sys ( nvlddmkm+d64c3 )
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sun Jul 25 10:20:57.221 2010 (UTC - 4:00)
System Uptime: 0 days 9:10:13.282
BugCheck A, {fffff80002f5ca26, 2, 0, fffff80002ce5042}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sun Jul 25 01:10:12.056 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:15.085
BugCheck A, {100, 2, 0, fffff80002cd7393}
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sun Jul 25 00:31:09.962 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:15.007
BugCheck A, {e, 2, 1, fffff80002c9852b}
Probably caused by : CI.dll ( CI!A_SHAUpdate+60 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 24 12:29:04.350 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:25.363
BugCheck 3B, {c0000005, fffff80002c89b05, fffff880046e2fd0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avguard.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Sat Jul 24 12:21:07.991 2010 (UTC - 4:00)
System Uptime: 1 days 0:58:50.005
BugCheck A, {fffffa00060010d0, 2, 0, fffff80002c7ec6e}
Probably caused by : cng.sys ( cng!GatherRandomKey+294 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
See less See more
Save
Like
S
The sfc.exe said "Windows resource protection found corrupt files but was unable to fix some of them" and saved a log file. I am attaching it. I also am attaching the two dump files that happened today.

I will run the other tests tonight. Thanks!

Attachments

Save
Like
usasma
The CBS.log file shows a couple of files that couldn't be repaired. But, in my limited experience, I don't think that they are related to this problem.

They are:
spwizimg.dll
themeui.dll
background.bmp

Try changing your theme and see if something happens to the system (if the themeui.dll is corrupted, there should be a problem when trying to change the theme).

Try locating background.bmp on your system and have a look at it to see if the image is corrupted.

2 different BSOD errors (still looks like hardware):
BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Mon Jul 26 18:47:17.036 2010 (UTC - 4:00)
System Uptime: 0 days 2:17:20.049
BugCheck 1E, {ffffffffc000001d, fffff880088372f0, 0, 0}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : Rt64win7.sys ( Rt64win7+46d70 )
BUGCHECK_STR:  0x1E_c000001d
PROCESS_NAME:  uTorrent.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Debug session time: Mon Jul 26 16:29:06.855 2010 (UTC - 4:00)
System Uptime: 0 days 1:52:37.478
BugCheck 1A, {411, fffff68000035970, 91b000017551a824, fffff68000035171}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  wlschost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
See less See more
Save
Like
1 - 13 of 13 Posts
Status
Not open for further replies.
Tech Support Forum
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!
Full Forum Listing
Explore Our Forums
Windows XP Support Windows 7 , Windows Vista Support Motherboards, Bios|UEFI & CPU Networking Support Laptop Support
Top