Hey, this is my first post here at SevenForums, so let me know if I've forgotten anything important. Basically, when I'm booting or restarting my computer, I get a BSOD error and the computer restarts itself. After several attempts, usually restarting 5 or 6 times, it finally reaches the desktop and runs completely fine, even with games and web browsing. I've searched other similar problems on the site, but have been unsuccessful in finding a solution. Basic information is as follows:
OS: Windows 7 Home Premium 64 bit OEM
Age: roughly 3 weeks since build completion
Mobo: Gigabyte 870A UD3
CPU: AMD Athlon II x4
HDD: Seagate Barracuda SATA 500G / 16mb cache
Graphics: Gigabyte w/ ATI Radeon HD4670 1G DDR3
Memory: G.Skill DDR3 2x2G
Power: Rosewill 500W
OS: Windows 7 Home Premium 64 bit OEM
Age: roughly 3 weeks since build completion
Mobo: Gigabyte 870A UD3
CPU: AMD Athlon II x4
HDD: Seagate Barracuda SATA 500G / 16mb cache
Graphics: Gigabyte w/ ATI Radeon HD4670 1G DDR3
Memory: G.Skill DDR3 2x2G
Power: Rosewill 500W
correction to original post:
I'm now experiencing crashes and BSOD stop errors in the middle of random activities, such as browsing through file folders and playing media files. I cannot provoke a crash, it just seems to happen randomly... and on start-up, of course.
I'm now experiencing crashes and BSOD stop errors in the middle of random activities, such as browsing through file folders and playing media files. I cannot provoke a crash, it just seems to happen randomly... and on start-up, of course.
�� Quote: Originally Posted by mzimmer4 
correction to original post:
I'm now experiencing crashes and BSOD stop errors in the middle of random activities, such as browsing through file folders and playing media files. I cannot provoke a crash, it just seems to happen randomly... and on start-up, of course.
I'm now experiencing crashes and BSOD stop errors in the middle of random activities, such as browsing through file folders and playing media files. I cannot provoke a crash, it just seems to happen randomly... and on start-up, of course.
Seems like the it's pointing to Windows Core Files. I would recommend to do some basic steps.
Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! � Captain Debugger
Then run SFC /SCANNOW Command - System File Checker
Enable Driver Verifier Using Driver Verifier to identify issues with Drivers
Hope this helps,
Captain
Ok, so after a few diagnostic tests... here's what I have so far.
Ran SeaTools for Windows (since I have a Seagate hard drive):
SMART Check - Fail
Short DST - Fail
Long DST - Fail
Short Generic - Pass
Long Generic - Pass
Ran Windows Memory Diagnostic:
No errors detected
Ran SFC / Scannow:
Did not find any integrity violations
Also, after one of the crashes the other day, I ran the built-in Windows Repair feature that pops up after a crash during start-up. It basically said that there was something wrong with my hard disk and it was unable to repair the problem automatically. Before researching this problem on SevenForums, I downloaded and ran HD Tuner and it told me that I had 4095 bad sector on the HDD and that it failed the Health Check. The only suggestions that it gave was to replace the hard drive.
Ran SeaTools for Windows (since I have a Seagate hard drive):
SMART Check - Fail
Short DST - Fail
Long DST - Fail
Short Generic - Pass
Long Generic - Pass
Ran Windows Memory Diagnostic:
No errors detected
Ran SFC / Scannow:
Did not find any integrity violations
Also, after one of the crashes the other day, I ran the built-in Windows Repair feature that pops up after a crash during start-up. It basically said that there was something wrong with my hard disk and it was unable to repair the problem automatically. Before researching this problem on SevenForums, I downloaded and ran HD Tuner and it told me that I had 4095 bad sector on the HDD and that it failed the Health Check. The only suggestions that it gave was to replace the hard drive.
I would also recommend a hard drive replacement.
First, try a couple of things.
Test your HD temps with Speedfan: SpeedFan - Access temperature sensor in your computer
Run a disk check. Open an elevated command prompt and enter chkdsk /r.
First, try a couple of things.
Test your HD temps with Speedfan: SpeedFan - Access temperature sensor in your computer
Run a disk check. Open an elevated command prompt and enter chkdsk /r.
Hello,
I would recommend to start backup up your data immediately and check if the HDD covers warranty. If so claim it. Or else it best to get a new one. Often there isn't much troubleshooting can be done if manufactures tools fails and gives error. I'm sorry my friend i wish i was more helpful in this case.
Hope this helps,
Captain
I would recommend to start backup up your data immediately and check if the HDD covers warranty. If so claim it. Or else it best to get a new one. Often there isn't much troubleshooting can be done if manufactures tools fails and gives error. I'm sorry my friend i wish i was more helpful in this case.
Hope this helps,
Captain
Yes, captain, I'm afraid that may be the route I end up going. But, I wanted to give an update before heading to work. After running chkdsk /r through the night, I awoke to a DOS-style screen from Windows Boot Manager, saying this at the bottom:
Error: 0cx0000428
Windows cannot verify the digital signature on the file.
Also with this message was some other information telling me to run Windows Repair (which have been unsuccessful in both identifying and repairing the problem).
Basically I wanted to verify that the hard drive was what was giving me the BSOD problems.
Error: 0cx0000428
Windows cannot verify the digital signature on the file.
Also with this message was some other information telling me to run Windows Repair (which have been unsuccessful in both identifying and repairing the problem).
Basically I wanted to verify that the hard drive was what was giving me the BSOD problems.
So this hard drive is still under warranty from Seagate... I will be sending it to get a replacement. Hopefully the next one will be error-free.
I've researched compatibility issues with Seagate hard drives and Windows 7 and found that many people experience problems with the drive not being recognized during the initial Windows setup (although the drive is recognized in BIOS). Perhaps I would avoid installation/partitioning problems with a Western Digital or other brand?
Just one more thing that I'm curious about... When I receive my new hard drive and go through the Windows 7 install again, am I going to run into problems activating Windows? I've read several sites that say that I won't; however, correct me if I'm wrong, but I thought that "OEM" meant that the OS can only be installed once. That is, it's tied to one "computer" (whereas retail versions are tied to one "user").
I've researched compatibility issues with Seagate hard drives and Windows 7 and found that many people experience problems with the drive not being recognized during the initial Windows setup (although the drive is recognized in BIOS). Perhaps I would avoid installation/partitioning problems with a Western Digital or other brand?
Just one more thing that I'm curious about... When I receive my new hard drive and go through the Windows 7 install again, am I going to run into problems activating Windows? I've read several sites that say that I won't; however, correct me if I'm wrong, but I thought that "OEM" meant that the OS can only be installed once. That is, it's tied to one "computer" (whereas retail versions are tied to one "user").
�� Quote: Originally Posted by mzimmer4 Just one more thing that I'm curious about... When I receive my new hard drive and go through the Windows 7 install again, am I going to run into problems activating Windows? I've read several sites that say that I won't; however, correct me if I'm wrong, but I thought that "OEM" meant that the OS can only be installed once. That is, it's tied to one "computer" (whereas retail versions are tied to one "user").
2) If you dont have such a disk, you have 2 options. You can order one from your OEM vendor (dell, HP whatever) for a small price. Heck, if you explain your circumstances to them, they might even ship the disk free.
The other option is to get hold of a generic win7 disk (borrow from a friend or download etc.), then install, and activate using the COA key at the back of or beneath the battery of your computer. You'll need to phone activate.
Activate Windows 7 by Phone
3) In case you mean, you've installed from a System builder's OEM disk (like the ones from Newegg etc.), those behave and activate like retail ones, except that MS has no responsibility for tech support. In that case, you would have activated ONLINE. To reactivate after reinstalling from a such a disk, you'll again need to go online and unless you've changed hardware like crazy in recent times, it should go through. Thats because certain weightages are assigned to certain hardware changes and simply changing a hdd should not upset the balance.
4) See, OEM activation is tied to the first computer it is installed on, you cant transfer the license to another machine. Thats about it.
Ok... so I ended up just buying another hard drive (Seagate 1TB) and reinstalled Windows on it. After copying some video files over, I wanted to take it for a spin. About 2 minutes in, I encountered another BSOD. Attached is a zip file containing some reports. Let me know what's up. Thanks in advance.
I immediately suspect your outdated Realtek drivers. Please install these ones: Realtek
...Summary of the Dumps:
Code:
Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Aug 26 20:36:16.707 2010 (UTC - 4:00) System Uptime: 0 days 4:06:07.501 BugCheck A, {30, 2, 1, fffff800028dd6ef} Probably caused by : afd.sys ( afd!AfdTimerWheelHandler+19d ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Ok, I'm not too sure about what to do next. I went to the Realtek site linked in the previous post, and clicked on the download for "Win7 and WinServer 2008 R2 Driver"... but it just downloaded a zip file with some other files inside. I'm kind of used to self-installing drivers that are available on discs and autorun files. What do I do with this zip file?
Also, after installing a buttload of updates from Windows Update, I installed some drivers (which is something I neglected to do in my haste after installing Windows again). Still nothing though, perhaps this Realtek thing is what's holding me back. I'll attach the most recent reports.
Also, after installing a buttload of updates from Windows Update, I installed some drivers (which is something I neglected to do in my haste after installing Windows again). Still nothing though, perhaps this Realtek thing is what's holding me back. I'll attach the most recent reports.
Go to Device Mananager, right-click on your Realtek card (in the Network Adapters section), and select "Update driver software". Then select "Browse my computer for software" and point it to the folder you have extracted the zip files to.
Ok, got the Realtek drivers installed... but I still seem to be having a problem with random crashes. Even with NO activity whatsoever, the system will crash and attempt to reboot. Sometimes it will sit on the BSOD for an indefinite length of time until I manually turn off the computer and power it on again. Other times, I get to the DOS-style screen where I have the option to run Windows Repair or Start Windows Normally. I tried running Windows Repair (which was recommended), but it simply crashed after selecting this option.
Also, after installing the driver, I clicked on the Start menu and got a message that said "Windows Explorer has stopped working..." shortly followed by another crash.
Attached are the most recent performance monitor reports and dump files.
Also, after installing the driver, I clicked on the Start menu and got a message that said "Windows Explorer has stopped working..." shortly followed by another crash.
Attached are the most recent performance monitor reports and dump files.
Hello,
Since you have replaced the Hard drive run the Diagnostic again maybe something wrong the cable or Motherboard itself. I assume you haven't connected your old Hard drive. If so please disconnect it and let the new one run. Anyhow here is the link Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! � Captain Debugger
Disconnected NEC Electronics USB 3.0 Host Controller from your USB Port for few days and see if that makes any difference.
Update the ASUS DRW-24B1ST Driver Acer DRW-24B1ST Drivers - Asus Drivers Download
Hope this helps,
Captain
Since you have replaced the Hard drive run the Diagnostic again maybe something wrong the cable or Motherboard itself. I assume you haven't connected your old Hard drive. If so please disconnect it and let the new one run. Anyhow here is the link Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! � Captain Debugger
Disconnected NEC Electronics USB 3.0 Host Controller from your USB Port for few days and see if that makes any difference.
Update the ASUS DRW-24B1ST Driver Acer DRW-24B1ST Drivers - Asus Drivers Download
Hope this helps,
Captain
Nah, the old hard drive is in the box ready to be returned to Seagate for warranty replacement... however, I DID just keep the old cable in line (for convenience purposes). I'll replace it with a new SATA cable and run the recommended hardware diagnostics afterward. Before I do though, something I'm curious about... Would plugging the hard drive into a different SATA port do anything? I have 4 SATA ports on my motherboard, one being used by the hard drive and the other being used for the eSATA plugin on the front of the case. Would I run into recognition problems or anything if I tried another port on the motherboard? Or is it safe to assume if one's bad, they're all bad?
�� Quote: Originally Posted by mzimmer4 Nah, the old hard drive is in the box ready to be returned to Seagate for warranty replacement... however, I DID just keep the old cable in line (for convenience purposes). I'll replace it with a new SATA cable and run the recommended hardware diagnostics afterward. Before I do though, something I'm curious about... Would plugging the hard drive into a different SATA port do anything? I have 4 SATA ports on my motherboard, one being used by the hard drive and the other being used for the eSATA plugin on the front of the case. Would I run into recognition problems or anything if I tried another port on the motherboard? Or is it safe to assume if one's bad, they're all bad?
Good Luck,
Captain
Hey Capt., had yet another question regarding a previous post of yours...
�� Quote: Originally Posted by Capt.Jack Sparrow
Disconnected NEC Electronics USB 3.0 Host Controller from your USB Port for few days and see if that makes any difference.
...is this something done inside the case on the motherboard? I believe that the only USB 3.0 ports are on the I/O panel that sticks out of the back of the case. I'm not sure if it is a cable that runs into a port, but I'll see in a couple minutes when I open it up.
�� Quote: Originally Posted by Capt.Jack Sparrow Disconnected NEC Electronics USB 3.0 Host Controller from your USB Port for few days and see if that makes any difference.
If you have a external Host Controller then disconnect it or else leave it alone.
So... after switching out the SATA cable with one supplied with the motherboard, I finally got my computer to turn back on (after having some grounding issues with the motherboard and chassis). The problem still exists though. Upon rebooting, I encountered 4 or 5 BSODs and finally got Windows to boot up as it should. Included are some more perfmon reports and dump files.
Also, before I changed out the SATA cable, I ran Memtest86+ and also Seatools for Windows. On the plus side, both checked out good (whereas the hard drive check failed miserably with the previous hard drive). Seems like my hardware is in good shape. You guys definitely know your diagnostics, I'll give you that. Please help before I jab a pencil in my ear!
Also, before I changed out the SATA cable, I ran Memtest86+ and also Seatools for Windows. On the plus side, both checked out good (whereas the hard drive check failed miserably with the previous hard drive). Seems like my hardware is in good shape. You guys definitely know your diagnostics, I'll give you that. Please help before I jab a pencil in my ear!
The crashes and restarts seem to be happening more frequently now. Nothing has really changed, but the system can't even stay on for more than 20 minutes or so without crashing... even with NO activity whatsoever. Is it possible that something is physically wrong with the motherboard? Or is this most likely a software issue?
If possible disconnect your DVD Drive for few hours and see if your System crashes. Its a vague thought Make sure you disconnect the cable from Motherboard. Its some Hardware troubleshooting always makes hard if its some Hardware component is causing the issue.
Try this free stress test: Free Software - GIMPS
Bugcheck:
Hope this helps,
Captain
Try this free stress test: Free Software - GIMPS
Quote:
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.
- "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).
The Test selection box and the stress.txt file describes what components that the program stresses.
- 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.
- "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).
The Test selection box and the stress.txt file describes what components that the program stresses.
Bugcheck:
Code:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000094, The exception code that was not handled Arg2: fffff800031b7548, The address that the exception occurred at Arg3: fffff880031a19f8, Exception Record Address Arg4: fffff880031a1260, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero. FAULTING_IP: nt!CmpDereferenceKeyControlBlock+5c fffff800`031b7548 f7b618060000 div eax,dword ptr [rsi+618h] EXCEPTION_RECORD: fffff880031a19f8 -- (.exr 0xfffff880031a19f8) ExceptionAddress: fffff800031b7548 (nt!CmpDereferenceKeyControlBlock+0x000000000000005c) ExceptionCode: c0000094 (Integer divide-by-zero) ExceptionFlags: 00000000 NumberParameters: 0 CONTEXT: fffff880031a1260 -- (.cxr 0xfffff880031a1260) rax=000000000a3a81f4 rbx=0000000000000000 rcx=00000000ee6b281c rdx=0000000000000000 rsi=fffff8a000027620 rdi=fffff8a003444a70 rip=fffff800031b7548 rsp=fffff880031a1c30 rbp=0000000000000001 r8=fffff8a000066808 r9=000000001ea79bab r10=fffff8a0034446f8 r11=fffffa80039f9b60 r12=00000000f8a5aa10 r13=0000000000000001 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl nz ac pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212 nt!CmpDereferenceKeyControlBlock+0x5c: fffff800`031b7548 f7b618060000 div eax,dword ptr [rsi+618h] ds:002b:fffff8a0`00027c38=00000000 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x7E PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero. LAST_CONTROL_TRANSFER: from fffff800031b79c4 to fffff800031b7548 STACK_TEXT: fffff880`031a1c30 fffff800`031b79c4 : 00000000`00000000 00000000`00000001 fffff8a0`00027620 fffffa80`039f9b60 : nt!CmpDereferenceKeyControlBlock+0x5c fffff880`031a1c80 fffff800`02ed1961 : fffff800`031b78dc fffff800`030695f8 fffffa80`039f9b60 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xe8 fffff880`031a1cb0 fffff800`03168c06 : 00000000`00000000 fffffa80`039f9b60 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111 fffff880`031a1d40 fffff800`02ea2c26 : fffff880`02f63180 fffffa80`039f9b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a19f0 00000000`00000000 : nt!KxStartSystemThread+0x16 FOLLOWUP_IP: nt!CmpDereferenceKeyControlBlock+5c fffff800`031b7548 f7b618060000 div eax,dword ptr [rsi+618h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!CmpDereferenceKeyControlBlock+5c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880031a1260 ; kb FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c BUCKET_ID: X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c Followup: MachineOwner PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it Arg2: 00000000000aaed8, page frame number Arg3: 0000000000000001, current share count Arg4: 0000000000000000, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002f1ff09 to fffff80002ebf740 STACK_TEXT: fffff880`02f8b638 fffff800`02f1ff09 : 00000000`0000004e 00000000`00000007 00000000`000aaed8 00000000`00000001 : nt!KeBugCheckEx fffff880`02f8b640 fffff800`02f33e5e : fffffa80`04938890 00000000`00000000 00000000`00000000 fffff880`0107efbc : nt! ?? ::FNODOBFM::`string'+0x16dc6 fffff880`02f8b680 fffff800`02ec1ae8 : fffffa80`0569000b 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x348b9 fffff880`02f8b710 fffff880`0187b8ee : 00000000`00000000 fffff800`02f73001 fffffa80`067d3428 00000000`00000000 : nt!IopfCompleteRequest+0x168 fffff880`02f8b7f0 fffff800`02ec1d26 : 00000000`00000000 fffff800`02e0b156 fffffa80`047dd4f0 00000000`00001000 : CLASSPNP!TransferPktComplete+0x1ce fffff880`02f8b870 fffff880`0104d41a : 00000000`00000000 00000000`00000001 fffffa80`067d3340 00000000`00000000 : nt!IopfCompleteRequest+0x3a6 fffff880`02f8b950 fffff880`0104d242 : fffffa80`067d3340 fffffa80`047dd4f0 fffffa80`067d3340 fffffa80`047e37d0 : ataport!IdeCompleteScsiIrp+0x62 fffff880`02f8b980 fffff880`01047e32 : 00000000`00000000 00000000`00000000 fffffa80`047e2a00 fffff800`02e31c60 : ataport!IdeCommonCrbCompletion+0x5a fffff880`02f8b9b0 fffff880`010507ed : fffffa80`047cf1a0 fffffa80`067d3340 00000000`00000000 fffffa80`067d3340 : ataport!IdeTranslateCompletedRequest+0x236 fffff880`02f8bae0 fffff880`010500ec : fffffa80`047cf1a0 00000000`00000000 fffffa80`047cf1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5 fffff880`02f8bc10 fffff800`02ecabfc : fffff880`02f63180 0000000c`e08a3b21 fffffa80`047cf050 fffffa80`047cf118 : ataport!IdePortCompletionDpc+0x1a8 fffff880`02f8bcd0 fffff800`02ec7eea : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`0104ff44 : nt!KiRetireDpcList+0x1bc fffff880`02f8bd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: CLASSPNP!TransferPktComplete+1ce fffff880`0187b8ee 837c243002 cmp dword ptr [rsp+30h],2 SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: CLASSPNP!TransferPktComplete+1ce FOLLOWUP_NAME: MachineOwner MODULE_NAME: CLASSPNP IMAGE_NAME: CLASSPNP.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11e FAILURE_BUCKET_ID: X64_0x4E_7_CLASSPNP!TransferPktComplete+1ce BUCKET_ID: X64_0x4E_7_CLASSPNP!TransferPktComplete+1ce Followup: MachineOwner --------- SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002fb40bf, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880073b8a70, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ExDeferredFreePool+233 fffff800`02fb40bf 4c395008 cmp qword ptr [rax+8],r10 CONTEXT: fffff880073b8a70 -- (.cxr 0xfffff880073b8a70) rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800395b6e0 rdx=fffff8a0091aafd0 rsi=fffff8a0091de000 rdi=fffff8a0091dc010 rip=fffff80002fb40bf rsp=fffff880073b9440 rbp=0000000000000004 r8=0000000000000000 r9=fffff8a0091aafd0 r10=fffff8a0091aafe0 r11=0000000000000001 r12=fffffa800395b280 r13=0000000000000000 r14=000000000000001d r15=0000000000000001 iopl=0 nv up ei ng nz ac po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297 nt!ExDeferredFreePool+0x233: fffff800`02fb40bf 4c395008 cmp qword ptr [rax+8],r10 ds:002b:00000000`00000008=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002fb40bf STACK_TEXT: fffff880`073b9440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x233 FOLLOWUP_IP: nt!ExDeferredFreePool+233 fffff800`02fb40bf 4c395008 cmp qword ptr [rax+8],r10 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ExDeferredFreePool+233 FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption STACK_COMMAND: .cxr 0xfffff880073b8a70 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+233 BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+233 Followup: Pool_corruption SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88000eef112, The address that the exception occurred at Arg3: fffff880031cb808, Exception Record Address Arg4: fffff880031cb070, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: Wdf01000!imp_WdfRequestWdmGetIrp+66 fffff880`00eef112 66394108 cmp word ptr [rcx+8],ax EXCEPTION_RECORD: fffff880031cb808 -- (.exr 0xfffff880031cb808) ExceptionAddress: fffff88000eef112 (Wdf01000!imp_WdfRequestWdmGetIrp+0x0000000000000066) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000057ffc5375f0 Attempt to read from address 0000057ffc5375f0 CONTEXT: fffff880031cb070 -- (.cxr 0xfffff880031cb070) rax=0000000000001008 rbx=fffffa8003ac8a10 rcx=0000057ffc5375e8 rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa800552b9c0 rip=fffff88000eef112 rsp=fffff880031cba40 rbp=0000057ffc621200 r8=000000000000064b r9=fffff88000f53310 r10=0000000000016a15 r11=fffff88002fd3180 r12=00000000002d0940 r13=0000000000000000 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 Wdf01000!imp_WdfRequestWdmGetIrp+0x66: fffff880`00eef112 66394108 cmp word ptr [rcx+8],ax ds:002b:0000057f`fc5375f0=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000057ffc5375f0 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b20e0 0000057ffc5375f0 FOLLOWUP_IP: cdrom!RequestPostWorkMcnRequest+45 fffff880`01905cb5 440fb6938b000000 movzx r10d,byte ptr [rbx+8Bh] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff88001905cb5 to fffff88000eef112 STACK_TEXT: fffff880`031cba40 fffff880`01905cb5 : 00000000`00000000 00000000`00000001 fffffa80`06553cb0 fffffa80`0552b9c0 : Wdf01000!imp_WdfRequestWdmGetIrp+0x66 fffff880`031cba90 fffff880`018fcdb8 : fffffa80`05633a00 0000057f`00000000 fffffa80`05633af0 fffff880`031cbb90 : cdrom!RequestPostWorkMcnRequest+0x45 fffff880`031cbb70 fffff880`00f0b6fb : 00000000`00000000 00000000`00000001 fffffa80`0552bf10 fffff800`0301f5f8 : cdrom!RequestProcessSerializedIoctl+0x590 fffff880`031cbc50 fffff800`03176c43 : fffffa80`05525720 fffff800`0307fe00 fffffa80`039ebb60 fffffa80`039ebb60 : Wdf01000!FxWorkItem::WorkItemThunk+0x113 fffff880`031cbc80 fffff800`02e87961 : fffff800`0316d800 fffff800`0316d8dc fffffa80`039ebb60 00000000`00000000 : nt!IopProcessWorkItem+0x23 fffff880`031cbcb0 fffff800`0311ec06 : 00000000`00000000 fffffa80`039ebb60 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111 fffff880`031cbd40 fffff800`02e58c26 : fffff880`02f63180 fffffa80`039ebb60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031cbd80 00000000`00000000 : fffff880`031cc000 fffff880`031c6000 fffff880`031cb770 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: cdrom!RequestPostWorkMcnRequest+45 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cdrom IMAGE_NAME: cdrom.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11a STACK_COMMAND: .cxr 0xfffff880031cb070 ; kb FAILURE_BUCKET_ID: X64_0x7E_cdrom!RequestPostWorkMcnRequest+45 BUCKET_ID: X64_0x7E_cdrom!RequestPostWorkMcnRequest+45 Followup: MachineOwner BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000003, the pool freelist is corrupt. Arg2: fffff8a00753bd00, the pool entry being checked. Arg3: fffff8a00753bd00, the read back flink freelist value (should be the same as 2). Arg4: fffff8a00753bf00, the read back blink freelist value (should be the same as 2). Debugging Details: ------------------ BUGCHECK_STR: 0x19_3 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002fb910b to fffff80002e86740 STACK_TEXT: fffff880`0828f8b8 fffff800`02fb910b : 00000000`00000019 00000000`00000003 fffff8a0`0753bd00 fffff8a0`0753bd00 : nt!KeBugCheckEx fffff880`0828f8c0 fffff800`02fbb4c1 : 00000000`00000001 fffff8a0`07db1a40 00000000`00000001 00000000`00000000 : nt!ExDeferredFreePool+0xc7b fffff880`0828f950 fffff800`02e8b8bc : fffffa80`0656d060 00000000`00000000 fffff880`656b6f54 fffffa80`03967e50 : nt!ExFreePoolWithTag+0x411 fffff880`0828fa00 fffff800`03156735 : fffff880`0828fca0 00000000`00000000 fffff8a0`07db1aa0 00000000`00000001 : nt!ObfDereferenceObject+0xdc fffff880`0828fa60 fffff800`02e85993 : fffffa80`0656d060 fffffa80`0656d060 fffffa80`0656d060 00000000`00000001 : nt!NtSetInformationThread+0x254 fffff880`0828fc20 00000000`7776fe2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`038ee988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7776fe2a STACK_COMMAND: kb FOLLOWUP_IP: nt!ExDeferredFreePool+c7b fffff800`02fb910b cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!ExDeferredFreePool+c7b FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+c7b BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+c7b Followup: Pool_corruption SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff96000142c6e, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88005dde0d0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: win32k!TimersProc+142 fffff960`00142c6e 488910 mov qword ptr [rax],rdx CONTEXT: fffff88005dde0d0 -- (.cxr 0xfffff88005dde0d0) rax=0000000000000000 rbx=fffff900c1aafa00 rcx=fffff900c1abc1e8 rdx=fffff900c1aafa60 rsi=0000000000004479 rdi=fffff900c1aafa18 rip=fffff96000142c6e rsp=fffff88005ddeaa0 rbp=0000000000000270 r8=fffffa80054560e8 r9=0000000000000000 r10=fffffffffffffffe r11=0000000000000000 r12=0000000000000000 r13=fffff9600035f2c0 r14=0000000000000002 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 win32k!TimersProc+0x142: fffff960`00142c6e 488910 mov qword ptr [rax],rdx ds:002b:00000000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff960001436a4 to fffff96000142c6e STACK_TEXT: fffff880`05ddeaa0 fffff960`001436a4 : 00000000`00000000 fffff960`0035fa90 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x142 fffff880`05ddeaf0 fffff960`000d46cc : fffffa80`0000007b 00000000`0000000f fffff880`00000001 00000000`00000000 : win32k!RawInputThread+0x9b4 fffff880`05ddebc0 fffff960`00153fa6 : fffffa80`00000002 fffff880`05da2f40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58 fffff880`05ddebf0 fffff800`02ecb993 : fffffa80`05cf6b60 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36 fffff880`05ddec20 000007fe`fd043d3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`00e6fe78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd043d3a FOLLOWUP_IP: win32k!TimersProc+142 fffff960`00142c6e 488910 mov qword ptr [rax],rdx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!TimersProc+142 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c483f STACK_COMMAND: .cxr 0xfffff88005dde0d0 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!TimersProc+142 BUCKET_ID: X64_0x3B_win32k!TimersProc+142 Followup: MachineOwner --------- MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff780c0000000 Arg3: 0000000000001d60 Arg4: 00000da700003ec0 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: WerFault.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ee1091 to fffff80002e71740 STACK_TEXT: fffff880`069bf2d8 fffff800`02ee1091 : 00000000`0000001a 00000000`00005003 fffff780`c0000000 00000000`00001d60 : nt!KeBugCheckEx fffff880`069bf2e0 fffff800`02e8e776 : fffff6fc`c0061af8 00000000`00000001 fffff880`00000001 ffffffff`ffff0001 : nt! ?? ::FNODOBFM::`string'+0x2a1af fffff880`069bf450 fffff800`02e9d7c1 : fffff980`0c35f000 00000000`0285f000 fffff880`00000004 fffff880`069bf638 : nt!MmCheckCachedPageStates+0x4d6 fffff880`069bf600 fffff800`02e9d434 : fffffa80`03d74e10 00000000`01961e40 fffff880`069bf740 00000000`00000000 : nt!CcMapAndCopyInToCache+0x301 fffff880`069bf6f0 fffff880`012e7fb8 : 00000000`0286f275 fffffa80`03d72400 fffff880`069bf7e0 fffffa80`00010000 : nt!CcCopyWrite+0x194 fffff880`069bf780 fffff880`01001132 : fffffa80`03d724a0 fffff880`01004732 00000000`00010000 00000000`00010001 : Ntfs!NtfsCopyWriteA+0x208 fffff880`069bf970 fffff880`01004c2a : fffff880`069bfa40 fffffa80`03d60968 00000000`01961e00 00000000`00010000 : fltmgr!FltpPerformFastIoCall+0xf2 fffff880`069bf9d0 fffff880`010227fe : 00000000`00010000 00000000`00000000 fffffa80`03d724a0 fffff880`069bfb40 : fltmgr!FltpPassThroughFastIo+0xda fffff880`069bfa10 fffff800`0318880e : fffffa80`03d72514 fffff880`069bfad8 00000000`00000000 fffffa80`03d72514 : fltmgr!FltpFastIoWrite+0x1ce fffff880`069bfab0 fffff800`02e70993 : 00000000`00000101 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x5ad fffff880`069bfbb0 00000000`76cffdda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000bb0c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76cffdda STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+2a1af fffff800`02ee1091 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2a1af FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a1af BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a1af Followup: MachineOwner --------- 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: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff88001014442, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b80e0 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: volsnap!VspLookupTableEntryWorker+12 fffff880`01014442 498911 mov qword ptr [r9],rdx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff88002ffb510 -- (.trap 0xfffff88002ffb510) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000009 rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa800490b8b0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88001014442 rsp=fffff88002ffb6a0 rbp=0000000000000000 r8=fffffa80060fc720 r9=0000000000000000 r10=0000000000000000 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc volsnap!VspLookupTableEntryWorker+0x12: fffff880`01014442 498911 mov qword ptr [r9],rdx ds:0003:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e7fca9 to fffff80002e80740 STACK_TEXT: fffff880`02ffb3c8 fffff800`02e7fca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`02ffb3d0 fffff800`02e7e920 : 00000000`00000200 fffffa80`0490b8b0 fffffa80`04295440 fffffa80`04914b60 : nt!KiBugCheckDispatch+0x69 fffff880`02ffb510 fffff880`01014442 : 00000000`00000000 fffffa80`04a69000 fffffa80`04903d90 fffffa80`04903c40 : nt!KiPageFault+0x260 fffff880`02ffb6a0 fffff880`01017f99 : fffffa80`0490bb7b 00000000`00000000 00000000`00000000 fffffa80`3fffffff : volsnap!VspLookupTableEntryWorker+0x12 fffff880`02ffb6d0 fffff800`02e82d26 : fffffa80`0490bb33 fffffa80`048fdcd0 fffffa80`0490b8b0 fffffa80`0490b8b0 : volsnap!VspLookupTableEntry+0x9 fffff880`02ffb710 fffff880`018c48ee : 00000000`00000000 fffff800`02f34001 fffffa80`04295140 00000000`00000000 : nt!IopfCompleteRequest+0x3a6 fffff880`02ffb7f0 fffff800`02e82d26 : 00000000`00000000 fffff800`033f1156 fffffa80`04804ea0 00000000`00004000 : CLASSPNP!TransferPktComplete+0x1ce fffff880`02ffb870 fffff880`00c5241a : 00000000`00000000 00000000`00000001 fffffa80`04295010 00000000`00000000 : nt!IopfCompleteRequest+0x3a6 fffff880`02ffb950 fffff880`00c52242 : fffffa80`04295010 fffffa80`04804ea0 fffffa80`04295010 fffffa80`048067d0 : ataport!IdeCompleteScsiIrp+0x62 fffff880`02ffb980 fffff880`00c4ce32 : 00000000`00000000 00000000`00000000 fffffa80`04805a00 fffff800`03417c60 : ataport!IdeCommonCrbCompletion+0x5a fffff880`02ffb9b0 fffff880`00c557ed : fffffa80`047ec1a0 fffffa80`04295010 00000000`00000000 fffffa80`04295010 : ataport!IdeTranslateCompletedRequest+0x236 fffff880`02ffbae0 fffff880`00c550ec : fffffa80`047ec1a0 00000000`00000000 fffffa80`047ec1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5 fffff880`02ffbc10 fffff800`02e8bbfc : fffff880`02fd3180 00000001`18ba4e65 fffffa80`047ec050 fffffa80`047ec118 : ataport!IdePortCompletionDpc+0x1a8 fffff880`02ffbcd0 fffff800`02e88eea : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`00c54f44 : nt!KiRetireDpcList+0x1bc fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: volsnap!VspLookupTableEntryWorker+12 fffff880`01014442 498911 mov qword ptr [r9],rdx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: volsnap!VspLookupTableEntryWorker+12 FOLLOWUP_NAME: MachineOwner MODULE_NAME: volsnap IMAGE_NAME: volsnap.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc128 FAILURE_BUCKET_ID: X64_0xD1_volsnap!VspLookupTableEntryWorker+12 BUCKET_ID: X64_0xD1_volsnap!VspLookupTableEntryWorker+12 Followup: MachineOwner --------- 3: kd> lmvm volsnap start end module name fffff880`01000000 fffff880`0104c000 volsnap (pdb symbols) k:\symbols\volsnap.pdb\EF40184814C849B584803DCF471EA1DE2\volsnap.pdb Loaded symbol image file: volsnap.sys Mapped memory image file: K:\Symbols\volsnap.sys\4A5BC1284c000\volsnap.sys Image path: \SystemRoot\system32\DRIVERS\volsnap.sys Image name: volsnap.sys Timestamp: Tue Jul 14 04:50:08 2009 (4A5BC128) CheckSum: 000568C8 ImageSize: 0004C000 File version: 6.1.7600.16385 Product version: 6.1.7600.16385 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft� Windows� Operating System InternalName: volsnap.sys OriginalFilename: volsnap.sys ProductVersion: 6.1.7600.16385 FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255) FileDescription: Volume Shadow Copy Driver LegalCopyright: � Microsoft Corporation. All rights reserved. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8800453ad45, The address that the exception occurred at Arg3: fffff880023bf6a8, Exception Record Address Arg4: fffff880023bef10, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 fffff880`0453ad45 ff90a8000000 call qword ptr [rax+0A8h] EXCEPTION_RECORD: fffff880023bf6a8 -- (.exr 0xfffff880023bf6a8) ExceptionAddress: fffff8800453ad45 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000079) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000000000a8 Attempt to read from address 00000000000000a8 CONTEXT: fffff880023bef10 -- (.cxr 0xfffff880023bef10) rax=0000000000000000 rbx=fffff8a008d4b840 rcx=fffffa8005ecfec0 rdx=fffffa8003c4c800 rsi=fffffa8005ec2000 rdi=fffffa8005ec2000 rip=fffff8800453ad45 rsp=fffff880023bf8e0 rbp=fffffa8006d1d050 r8=fffffa8003cc5c00 r9=0000000000000000 r10=0000000000000000 r11=0000000000000006 r12=fffffa8003c4c800 r13=0000000000000000 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x79: fffff880`0453ad45 ff90a8000000 call qword ptr [rax+0A8h] ds:002b:00000000`000000a8=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 00000000000000a8 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ae0e0 00000000000000a8 FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 fffff880`0453ad45 ff90a8000000 call qword ptr [rax+0A8h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff88004537ed3 to fffff8800453ad45 STACK_TEXT: fffff880`023bf8e0 fffff880`04537ed3 : 00000000`00000000 fffffa80`03cf0018 00000000`00000003 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x79 fffff880`023bf910 fffff880`0455265d : 00000000`00000000 fffff8a0`08cf44f0 fffffa80`00000000 fffffa80`03cc5c30 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f fffff880`023bfae0 fffff880`04552398 : fffff880`009ecf40 fffff880`04551d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`023bfcd0 fffff880`04551e96 : 00000000`00000000 fffffa80`03c7a830 00000000`00000080 fffffa80`054e4010 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`023bfd00 fffff800`0311ac06 : 00000000`0279c5bc fffffa80`05ea9770 fffffa80`0396c890 fffffa80`05ea9770 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`023bfd40 fffff800`02e54c26 : fffff880`009e8180 fffffa80`05ea9770 fffff880`009f2fc0 fffff880`01268534 : nt!PspSystemThreadStartup+0x5a fffff880`023bfd80 00000000`00000000 : fffff880`023c0000 fffff880`023ba000 fffff880`023bf690 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 STACK_COMMAND: .cxr 0xfffff880023bef10 ; kb FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 Followup: MachineOwner --------- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002fa790d, The address that the exception occurred at Arg3: fffff880031af078, Exception Record Address Arg4: fffff880031ae8e0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ExAllocatePoolWithTag+53d fffff800`02fa790d 48895808 mov qword ptr [rax+8],rbx EXCEPTION_RECORD: fffff880031af078 -- (.exr 0xfffff880031af078) ExceptionAddress: fffff80002fa790d (nt!ExAllocatePoolWithTag+0x000000000000053d) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880031ae8e0 -- (.cxr 0xfffff880031ae8e0) rax=69634d4300010103 rbx=fffffa800395a2a0 rcx=fffff8a0034207a0 rdx=000000000000001c rsi=0000000000001000 rdi=0000000000000001 rip=fffff80002fa790d rsp=fffff880031af2b0 rbp=fffffa800395a140 r8=0000000000000001 r9=fffffa800395a2a0 r10=fffffa800395a148 r11=0000000000000001 r12=0000000000000003 r13=0000000000000000 r14=fffffa80039ff040 r15=0000000065536f49 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!ExAllocatePoolWithTag+0x53d: fffff800`02fa790d 48895808 mov qword ptr [rax+8],rbx ds:002b:69634d43`0001010b=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ab0e0 ffffffffffffffff FOLLOWUP_IP: USBPORT!USBPORT_CreateRootHubPdo+16e fffff880`048f45ae 488d4c2468 lea rcx,[rsp+68h] BUGCHECK_STR: 0x7E LOCK_ADDRESS: fffff80003077400 -- (!locks fffff80003077400) Resource @ nt!PiEngineLock (0xfffff80003077400) Available WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. 1 total locks PNP_TRIAGE: Lock address : 0xfffff80003077400 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from fffff800031a211b to fffff80002fa790d STACK_TEXT: fffff880`031af2b0 fffff800`031a211b : fffffa80`00000001 fffff8a0`00001540 00000000`00000000 fffff880`00000000 : nt!ExAllocatePoolWithTag+0x53d fffff880`031af3a0 fffff800`030e19d8 : 00000000`0000002a 00000000`00000002 fffff880`031af548 fffff800`02e75d26 : nt! ?? ::NNGAKEGL::`string'+0x9d1d fffff880`031af400 fffff800`030e0208 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`031af638 : nt!IopCreateDefaultDeviceSecurityDescriptor+0x88 fffff880`031af450 fffff880`048f45ae : fffffa80`055dc801 fffffa80`054ac1a0 fffffa80`054ac050 00000000`00000000 : nt!IoCreateDevice+0xa8 fffff880`031af5d0 fffff880`048ee3f9 : fffffa80`054ac1a0 fffffa80`055dc6f0 fffffa80`055dc850 fffffa80`055dc850 : USBPORT!USBPORT_CreateRootHubPdo+0x16e fffff880`031af710 fffff880`048d98d5 : 00000000`00000000 fffff880`031af880 fffffa80`055dc6f0 fffffa80`039bea20 : USBPORT!USBPORT_FdoPnP+0xb91 fffff880`031af7c0 fffff800`0323206e : 00000000`00000000 00000000`00000000 fffffa80`056f4810 fffff880`02f63180 : USBPORT!USBPORT_DispatchPnP+0x1d fffff880`031af7f0 fffff800`032323da : 00000000`00000000 fffffa80`056f4810 fffff800`02f72d30 00000000`00000000 : nt!PnpAsynchronousCall+0xce fffff880`031af830 fffff800`032346c7 : fffff800`030771c0 fffffa80`043c9b10 00000000`00000002 00000000`00000000 : nt!PnpQueryDeviceRelations+0xfa fffff880`031af8f0 fffff800`032602cc : fffffa80`043c9b10 fffffa80`03a3003c fffffa80`03a31d90 00000000`00000002 : nt!PipEnumerateDevice+0x117 fffff880`031af950 fffff800`032607fc : fffff800`03074d80 00000000`00000000 00000000`00000001 fffff800`030e0840 : nt!PipProcessDevNodeTree+0x21c fffff880`031afbc0 fffff800`02f75382 : 00000001`00000003 fffff800`030185f8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c fffff880`031afc10 fffff800`02e80961 : fffff800`02f75080 fffff800`030df001 fffff800`03018500 480fe783`c78b4800 : nt!PnpDeviceActionWorker+0x302 fffff880`031afcb0 fffff800`03117c06 : 000001fc`e9c00000 fffffa80`039ff040 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111 fffff880`031afd40 fffff800`02e51c26 : fffff880`02f63180 fffffa80`039ff040 fffff880`02f6dfc0 8b4cf702`41f7f748 : nt!PspSystemThreadStartup+0x5a fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`031af0f0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: USBPORT!USBPORT_CreateRootHubPdo+16e FOLLOWUP_NAME: MachineOwner MODULE_NAME: USBPORT IMAGE_NAME: USBPORT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07 STACK_COMMAND: .cxr 0xfffff880031ae8e0 ; kb FAILURE_BUCKET_ID: X64_0x7E_USBPORT!USBPORT_CreateRootHubPdo+16e BUCKET_ID: X64_0x7E_USBPORT!USBPORT_CreateRootHubPdo+16e Followup: MachineOwner --------- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: 00000000000cef03, The address that the exception occurred at Arg3: fffff880031bd668, Exception Record Address Arg4: fffff880031bced0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: +16 00000000`000cef03 ?? ??? EXCEPTION_RECORD: fffff880031bd668 -- (.exr 0xfffff880031bd668) ExceptionAddress: 00000000000cef03 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 00000000000cef03 Attempt to execute non-executable address 00000000000cef03 CONTEXT: fffff880031bced0 -- (.cxr 0xfffff880031bced0) rax=00000000000cef03 rbx=0000000000000000 rcx=00000000000cef05 rdx=fffffa800529ccd0 rsi=fffffa800481b1b0 rdi=fffffa800529cc88 rip=00000000000cef03 rsp=fffff880031bd8a8 rbp=fffff880031bd918 r8=fffff880031bd901 r9=0000000000000001 r10=fffffa8004c56d30 r11=fffff880031bd870 r12=fffffa8004929c28 r13=fffff880031bdb20 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei ng nz ac pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010292 00000000`000cef03 ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 00000000000cef03 WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800031080e0 00000000000cef03 FOLLOWUP_IP: ataport!IdePortTranslateSrbToCrb+4f fffff880`010405ab 3bc3 cmp eax,ebx FAILED_INSTRUCTION_ADDRESS: +64cb952f0091de0c 00000000`000cef03 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff880010405ab to 00000000000cef03 STACK_TEXT: fffff880`031bd8a8 fffff880`010405ab : fffffa80`0529cc88 fffffa80`04929b10 fffff880`00000020 fffffa80`05325001 : 0xcef03 fffff880`031bd8b0 fffff880`010449b3 : fffffa80`0481b060 fffffa80`0529cc88 fffffa80`0481b1b0 fffff880`00e2f016 : ataport!IdePortTranslateSrbToCrb+0x4f fffff880`031bd8e0 fffff880`010404ee : fffffa80`04929b10 00000000`00000000 fffffa80`03957e40 fffffa80`04929b10 : ataport!IdePortPdoDispatch+0x87 fffff880`031bd910 fffff880`00e29787 : fffffa80`04929b10 fffffa80`04929c01 fffffa80`04929c01 fffffa80`04929c48 : ataport!IdePortDispatch+0x16 fffff880`031bd940 fffff880`00e31751 : fffff880`00e4fb50 fffff880`00c0b77b fffff880`031bdb20 fffffa80`04929c28 : ACPI!ACPIDispatchForwardIrp+0x37 fffff880`031bd970 fffff880`00e29a1f : fffff880`00e4fb50 fffffa80`039a0a00 fffffa80`04929b10 fffff880`00c877c0 : ACPI!ACPIIrpDispatchDeviceControl+0x75 fffff880`031bd9a0 fffff880`00c0e0c2 : fffffa80`05525540 fffff880`031bdb50 fffff880`00c877c0 fffffa80`05325020 : ACPI!ACPIDispatchIrp+0x12b fffff880`031bda20 fffff880`00c2359f : fffffa80`05325020 fffffa80`00000000 00000000`00000000 fffff880`019b05d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a fffff880`031bdad0 fffff880`019cb012 : fffffa80`00000020 fffffa80`05525540 fffffa80`05325020 fffffa80`0531ca20 : Wdf01000!imp_WdfRequestSend+0x24b fffff880`031bdb20 fffff880`019c1dab : fffffa80`0529cc00 0000057f`f9414bf8 00000000`00000000 fffff880`0177d180 : cdrom!RequestSendMcnRequest+0x5a fffff880`031bdb70 fffff880`00c406fb : 00000000`00000000 00000000`00000000 fffffa80`0531dbf0 fffff800`030755f8 : cdrom!RequestProcessSerializedIoctl+0x583 fffff880`031bdc50 fffff800`031ccc43 : fffffa80`0531fc70 fffffa80`049fde00 fffffa80`039ff680 fffffa80`039ff680 : Wdf01000!FxWorkItem::WorkItemThunk+0x113 fffff880`031bdc80 fffff800`02edd961 : fffff800`03075500 fffff800`031ccc20 fffffa80`039ff680 00000000`00000000 : nt!IopProcessWorkItem+0x23 fffff880`031bdcb0 fffff800`03174c06 : 00000000`00000000 fffffa80`039ff680 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111 fffff880`031bdd40 fffff800`02eaec26 : fffff880`02f63180 fffffa80`039ff680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd9f0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: ataport!IdePortTranslateSrbToCrb+4f FOLLOWUP_NAME: MachineOwner MODULE_NAME: ataport IMAGE_NAME: ataport.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc118 STACK_COMMAND: .cxr 0xfffff880031bced0 ; kb FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_ataport!IdePortTranslateSrbToCrb+4f BUCKET_ID: X64_0x7E_BAD_IP_ataport!IdePortTranslateSrbToCrb+4f Followup: MachineOwner SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff800031a4916, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880069e3ab0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!CmpAllocateKeyControlBlock+72 fffff800`031a4916 48895808 mov qword ptr [rax+8],rbx CONTEXT: fffff880069e3ab0 -- (.cxr 0xfffff880069e3ab0) rax=0000000000000000 rbx=fffff800030cb040 rcx=fffff8a002969ee8 rdx=fffff880069e44e8 rsi=fffff8a0006f9010 rdi=0000000000000001 rip=fffff800031a4916 rsp=fffff880069e4480 rbp=000000000249f1f8 r8=fffff8a00696e1fc r9=fffff8a002b656f8 r10=fffff8a008d9c132 r11=0000000000000000 r12=0000000000000000 r13=ffffffffffffffff r14=fffff8a00696e1fc r15=fffff8a002b656f8 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!CmpAllocateKeyControlBlock+0x72: fffff800`031a4916 48895808 mov qword ptr [rax+8],rbx ds:002b:00000000`00000008=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800031a4916 STACK_TEXT: fffff880`069e4480 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpAllocateKeyControlBlock+0x72 FOLLOWUP_IP: nt!CmpAllocateKeyControlBlock+72 fffff800`031a4916 48895808 mov qword ptr [rax+8],rbx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!CmpAllocateKeyControlBlock+72 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880069e3ab0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!CmpAllocateKeyControlBlock+72 BUCKET_ID: X64_0x3B_nt!CmpAllocateKeyControlBlock+72 Followup: MachineOwner --------- NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800318c368 Arg3: fffff8800318bbd0 Arg4: fffff80002fb0327 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800318c368 -- (.exr 0xfffff8800318c368) ExceptionAddress: fffff80002fb0327 (nt!ExFreePoolWithTag+0x0000000000000277) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000080 Attempt to read from address 0000000000000080 CONTEXT: fffff8800318bbd0 -- (.cxr 0xfffff8800318bbd0) rax=0000000000000200 rbx=fffff8a008475a70 rcx=00000000000005a5 rdx=fffff88002f64180 rsi=0000000000000003 rdi=0000000000000001 rip=fffff80002fb0327 rsp=fffff8800318c5a0 rbp=0000000000000000 r8=0000000000002d28 r9=0000000000000030 r10=fffff80002e0b000 r11=0000000000000121 r12=0000000000000003 r13=fffff8a008475a80 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!ExFreePoolWithTag+0x277: fffff800`02fb0327 458b8780000000 mov r8d,dword ptr [r15+80h] ds:002b:00000000`00000080=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000080 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b30e0 0000000000000080 FOLLOWUP_IP: fileinfo!FIStreamLog+89 fffff880`010cf55d 4c8b1534c5ffff mov r10,qword ptr [fileinfo!FIGlobals+0x798 (fffff880`010cba98)] FAULTING_IP: nt!ExFreePoolWithTag+277 fffff800`02fb0327 458b8780000000 mov r8d,dword ptr [r15+80h] BUGCHECK_STR: 0x24 DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff800032c7bec to fffff80002fb0327 STACK_TEXT: fffff880`0318c5a0 fffff800`032c7bec : fffff800`0301cc88 fffff880`04168332 00000000`4b466650 00000000`00000000 : nt!ExFreePoolWithTag+0x277 fffff880`0318c650 fffff800`02f9c559 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`0847e140 : nt!PfpRpFileKeyUpdate+0x4cc fffff880`0318c6e0 fffff880`010cf55d : 00000000`00000000 00000000`00000000 fffff880`0318c860 fffff880`0318ca90 : nt!PfFileInfoNotify+0x549 fffff880`0318c770 fffff880`010cf746 : fffff8a0`07dd75c0 fffff8a0`07dd75c0 00000000`00000000 00000000`00000000 : fileinfo!FIStreamLog+0x89 fffff880`0318c840 fffff880`0108865e : fffff880`0416cecc 00000000`00000000 ffffffff`ffffffff fffffa80`03d2f590 : fileinfo!FIStreamCleanup+0x96 fffff880`0318c890 fffff880`010a422d : fffff8a0`07dd7578 fffff880`0107a000 00000000`00000000 00000000`00000001 : fltmgr!DoFreeContext+0x7e fffff880`0318c8c0 fffff880`0109fbc1 : fffffa80`04abf010 00000000`00000130 fffff8a0`0847e140 fffff8a0`0847e140 : fltmgr! ?? ::NNGAKEGL::`string'+0x1196 fffff880`0318c8f0 fffff880`0109fb7b : fffffa80`04abf010 fffff8a0`0847e3a8 fffffa80`04abf010 00000000`00000000 : fltmgr!CleanupStreamListCtrl+0x21 fffff880`0318c920 fffff800`0316a896 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`0719c660 : fltmgr!DeleteStreamListCtrlCallback+0x6b fffff880`0318c950 fffff880`012b0bcc : fffff8a0`0847e140 fffffa80`03a70680 fffff880`0318ca28 00000000`00000706 : nt!FsRtlTeardownPerStreamContexts+0xe2 fffff880`0318c9a0 fffff880`012b08d5 : 00000000`00000000 00000000`00000000 fffff800`03020500 00000000`00000001 : Ntfs!NtfsDeleteScb+0x108 fffff880`0318c9e0 fffff880`01223cb4 : fffff8a0`0847e040 fffff8a0`0847e140 fffff800`03020500 00000000`00000000 : Ntfs!NtfsRemoveScb+0x61 fffff880`0318ca20 fffff880`012ae2dc : fffff8a0`0847e010 fffff800`030205a0 fffff880`0318cb52 fffffa80`05628010 : Ntfs!NtfsPrepareFcbForRemoval+0x50 fffff880`0318ca50 fffff880`0122c882 : fffffa80`05628010 fffffa80`05628010 fffff8a0`0847e010 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xdc fffff880`0318cad0 fffff880`012c5813 : fffffa80`05628010 fffff800`030205a0 fffff8a0`0847e010 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2 fffff880`0318cb10 fffff880`0129f38f : fffffa80`05628010 fffff8a0`0847e140 fffff8a0`0847e010 fffffa80`04a70180 : Ntfs!NtfsCommonClose+0x353 fffff880`0318cbe0 fffff800`02e88961 : 00000000`00000000 fffff800`03136d00 fffffa80`03a70601 00000000`00000002 : Ntfs!NtfsFspClose+0x15f fffff880`0318ccb0 fffff800`0311fc06 : 00000000`00000000 fffffa80`03a70680 00000000`00000080 fffffa80`03a4d040 : nt!ExpWorkerThread+0x111 fffff880`0318cd40 fffff800`02e59c26 : fffff880`02f64180 fffffa80`03a70680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318c9f0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: fileinfo!FIStreamLog+89 FOLLOWUP_NAME: MachineOwner MODULE_NAME: fileinfo IMAGE_NAME: fileinfo.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc481 STACK_COMMAND: .cxr 0xfffff8800318bbd0 ; kb FAILURE_BUCKET_ID: X64_0x24_fileinfo!FIStreamLog+89 BUCKET_ID: X64_0x24_fileinfo!FIStreamLog+89 Followup: MachineOwner --------- SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff960000c6f14, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88006ea5660, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: win32k!DecPaintCount+4 fffff960`000c6f14 8382e0010000ff add dword ptr [rdx+1E0h],0FFFFFFFFh CONTEXT: fffff88006ea5660 -- (.cxr 0xfffff88006ea5660) rax=0000000000000000 rbx=0000000000000001 rcx=fffff900c080ff40 rdx=000000000002c018 rsi=0000000000000000 rdi=fffff900c080ff40 rip=fffff960000c6f14 rsp=fffff88006ea6038 rbp=fffff9600035ac00 r8=0000000000000000 r9=0000000000000000 r10=fffff80002e01000 r11=fffff88006ea6030 r12=0000000000000000 r13=ffffffffffffffff r14=0000000000000002 r15=00000000000500b2 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 win32k!DecPaintCount+0x4: fffff960`000c6f14 8382e0010000ff add dword ptr [rdx+1E0h],0FFFFFFFFh ds:002b:00000000`0002c1f8=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960000c6f14 STACK_TEXT: fffff880`06ea6038 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!DecPaintCount+0x4 FOLLOWUP_IP: win32k!DecPaintCount+4 fffff960`000c6f14 8382e0010000ff add dword ptr [rdx+1E0h],0FFFFFFFFh SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!DecPaintCount+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c483f STACK_COMMAND: .cxr 0xfffff88006ea5660 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!DecPaintCount+4 BUCKET_ID: X64_0x3B_win32k!DecPaintCount+4 Followup: MachineOwner CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa8005d81b30, Terminating object Arg3: fffffa8005d81e10, Process image file name Arg4: fffff800031d75d0, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: fffffa8005d81b30 IMAGE_NAME: wininit.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: wininit FAULTING_MODULE: 0000000000000000 PROCESS_NAME: wininit.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0xF4_C0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: fffff880`05fd9b08 fffff800`03258652 : 00000000`000000f4 00000000`00000003 fffffa80`05d81b30 fffffa80`05d81e10 : nt!KeBugCheckEx fffff880`05fd9b10 fffff800`032013e3 : ffffffff`ffffffff fffffa80`05d7db60 fffffa80`05d81b30 fffffa80`05d81b30 : nt!PspCatchCriticalBreak+0x92 fffff880`05fd9b50 fffff800`0318980c : ffffffff`ffffffff 00000000`00000001 fffffa80`05d81b30 fffffa80`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17946 fffff880`05fd9ba0 fffff800`02ecb993 : fffffa80`05d81b30 000007ff`c0000005 00000000`c0000001 fffffa80`05d7db60 : nt!NtTerminateProcess+0x20c fffff880`05fd9c20 00000000`777c001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0018f2a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777c001a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe Followup: MachineOwner SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000094, The exception code that was not handled Arg2: fffff800031b7548, The address that the exception occurred at Arg3: fffff880031a19f8, Exception Record Address Arg4: fffff880031a1260, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero. FAULTING_IP: nt!CmpDereferenceKeyControlBlock+5c fffff800`031b7548 f7b618060000 div eax,dword ptr [rsi+618h] EXCEPTION_RECORD: fffff880031a19f8 -- (.exr 0xfffff880031a19f8) ExceptionAddress: fffff800031b7548 (nt!CmpDereferenceKeyControlBlock+0x000000000000005c) ExceptionCode: c0000094 (Integer divide-by-zero) ExceptionFlags: 00000000 NumberParameters: 0 CONTEXT: fffff880031a1260 -- (.cxr 0xfffff880031a1260) rax=000000000a3a81f4 rbx=0000000000000000 rcx=00000000ee6b281c rdx=0000000000000000 rsi=fffff8a000027620 rdi=fffff8a003444a70 rip=fffff800031b7548 rsp=fffff880031a1c30 rbp=0000000000000001 r8=fffff8a000066808 r9=000000001ea79bab r10=fffff8a0034446f8 r11=fffffa80039f9b60 r12=00000000f8a5aa10 r13=0000000000000001 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl nz ac pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212 nt!CmpDereferenceKeyControlBlock+0x5c: fffff800`031b7548 f7b618060000 div eax,dword ptr [rsi+618h] ds:002b:fffff8a0`00027c38=00000000 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x7E PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero. LAST_CONTROL_TRANSFER: from fffff800031b79c4 to fffff800031b7548 STACK_TEXT: fffff880`031a1c30 fffff800`031b79c4 : 00000000`00000000 00000000`00000001 fffff8a0`00027620 fffffa80`039f9b60 : nt!CmpDereferenceKeyControlBlock+0x5c fffff880`031a1c80 fffff800`02ed1961 : fffff800`031b78dc fffff800`030695f8 fffffa80`039f9b60 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xe8 fffff880`031a1cb0 fffff800`03168c06 : 00000000`00000000 fffffa80`039f9b60 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111 fffff880`031a1d40 fffff800`02ea2c26 : fffff880`02f63180 fffffa80`039f9b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a19f0 00000000`00000000 : nt!KxStartSystemThread+0x16 FOLLOWUP_IP: nt!CmpDereferenceKeyControlBlock+5c fffff800`031b7548 f7b618060000 div eax,dword ptr [rsi+618h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!CmpDereferenceKeyControlBlock+5c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880031a1260 ; kb FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c BUCKET_ID: X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c Followup: MachineOwner ---------
Captain
Hi -
16 BSODs < 24 hours; 9 different bugchecks is indicative of unknown hardware failure.
When you replaced the HDD, did you install Windows 7 on to it from DVD or use image from old HDD?
At this time, I would suggest that you wipe the HDD clean and reinstall Windows 7. See if system is stable before installing any 3rd party apps.
Use KillDisk to wipe HDD --> Format HDD jcgriff2.com
Windbg Logs
--> http://jcgriff2.com/dbug_logs/_99-db..._jcgriff2_.txt
--> http://jcgriff2.com/dbug_logs/_99-db...riff2_.txt.zip
Regards. . .
jcgriff2
`
BSOD BUGCHECK SUMMARY
16 BSODs < 24 hours; 9 different bugchecks is indicative of unknown hardware failure.
When you replaced the HDD, did you install Windows 7 on to it from DVD or use image from old HDD?
At this time, I would suggest that you wipe the HDD clean and reinstall Windows 7. See if system is stable before installing any 3rd party apps.
Use KillDisk to wipe HDD --> Format HDD jcgriff2.com
Windbg Logs
--> http://jcgriff2.com/dbug_logs/_99-db..._jcgriff2_.txt
--> http://jcgriff2.com/dbug_logs/_99-db...riff2_.txt.zip
Regards. . .
jcgriff2
`
BSOD BUGCHECK SUMMARY
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 20:47:05.418 2010 (GMT-4) System Uptime: 0 days 0:00:13.838 Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceKeyControlBlock+5c ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x7E PROCESS_NAME: System Bugcheck code 1000007E Arguments ffffffff`c0000094 fffff800`031b7548 fffff880`031a19f8 fffff880`031a1260 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 20:45:20.469 2010 (GMT-4) System Uptime: 0 days 0:00:20.264 BugCheck F4, {3, fffffa8005d81b30, fffffa8005d81e10, fffff800031d75d0} Probably caused by : wininit.exe PROCESS_NAME: wininit.exe BUGCHECK_STR: 0xF4_C0000005 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT Bugcheck code 000000F4 Arguments 00000000`00000003 fffffa80`05d81b30 fffffa80`05d81e10 fffff800`031d75d0 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 16:33:03.647 2010 (GMT-4) System Uptime: 0 days 0:21:13.067 Probably caused by : win32k.sys ( win32k!DecPaintCount+4 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe Bugcheck code 0000003B Arguments 00000000`c0000005 fffff960`000c6f14 fffff880`06ea5660 00000000`00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 16:11:23.374 2010 (GMT-4) System Uptime: 0 days 0:26:07.794 Probably caused by : fileinfo.sys ( fileinfo!FIStreamLog+89 ) PROCESS_NAME: System BUGCHECK_STR: 0x24 DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE Bugcheck code 00000024 Arguments 00000000`001904fb fffff880`0318c368 fffff880`0318bbd0 fffff800`02fb0327 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 15:27:03.255 2010 (GMT-4) System Uptime: 0 days 0:07:09.050 Probably caused by : ntkrnlmp.exe ( nt!CmpAllocateKeyControlBlock+72 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe Bugcheck code 0000003B Arguments 00000000`c0000005 fffff800`031a4916 fffff880`069e3ab0 00000000`00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 15:19:27.579 2010 (GMT-4) System Uptime: 0 days 0:05:06.000 Probably caused by : ataport.SYS ( ataport!IdePortTranslateSrbToCrb+4f ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System BUGCHECK_STR: 0x7E Bugcheck code 1000007E Arguments ffffffff`c0000005 00000000`000cef03 fffff880`031bd668 fffff880`031bced0 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 13:48:24.983 2010 (GMT-4) System Uptime: 0 days 0:00:11.778 Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_CreateRootHubPdo+16e ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System BUGCHECK_STR: 0x7E Bugcheck code 1000007E Arguments ffffffff`c0000005 fffff800`02fa790d fffff880`031af078 fffff880`031ae8e0 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 07:31:52.126 2010 (GMT-4) System Uptime: 0 days 0:23:12.921 Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 ) PROCESS_NAME: System BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE Bugcheck code 1000007E Arguments ffffffff`c0000005 fffff880`0453ad45 fffff880`023bf6a8 fffff880`023bef10 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 07:08:06.820 2010 (GMT-4) System Uptime: 0 days 0:28:34.240 BugCheck D1, {0, 2, 1, fffff88001014442} Probably caused by : volsnap.sys ( volsnap!VspLookupTableEntryWorker+12 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System Bugcheck code 000000D1 Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff880`01014442 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 06:38:31.920 2010 (GMT-4) System Uptime: 0 days 0:16:31.714 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a1af ) BUGCHECK_STR: 0x1a_5003 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: WerFault.exe Bugcheck code 0000001A Arguments 00000000`00005003 fffff780`c0000000 00000000`00001d60 00000da7`00003ec0 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 06:20:58.639 2010 (GMT-4) System Uptime: 0 days 0:10:10.434 Probably caused by : win32k.sys ( win32k!TimersProc+142 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: csrss.exe Bugcheck code 0000003B Arguments 00000000`c0000005 fffff960`00142c6e fffff880`05dde0d0 00000000`00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 06:09:47.652 2010 (GMT-4) System Uptime: 0 days 0:05:20.072 Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c7b ) BUGCHECK_STR: 0x19_3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe Bugcheck code 00000019 Arguments 00000000`00000003 fffff8a0`0753bd00 fffff8a0`0753bd00 fffff8a0`0753bf00 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 06:03:26.219 2010 (GMT-4) System Uptime: 0 days 2:48:30.014 Probably caused by : cdrom.sys ( cdrom!RequestPostWorkMcnRequest+45 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System BUGCHECK_STR: 0x7E Bugcheck code 1000007E Arguments ffffffff`c0000005 fffff880`00eef112 fffff880`031cb808 fffff880`031cb070 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 03:13:55.448 2010 (GMT-4) System Uptime: 0 days 0:11:50.243 Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe Bugcheck code 0000003B Arguments 00000000`c0000005 fffff800`02fb40bf fffff880`073b8a70 00000000`00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 03:01:01.890 2010 (GMT-4) System Uptime: 0 days 5:35:33.685 Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce ) BUGCHECK_STR: 0x4E_7 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System Bugcheck code 0000004E Arguments 00000000`00000007 00000000`000aaed8 00000000`00000001 00000000`00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Aug 26 20:36:16.707 2010 (GMT-4) System Uptime: 0 days 4:06:07.501 Probably caused by : afd.sys ( afd!AfdTimerWheelHandler+19d ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System Bugcheck code 0000000A Arguments 00000000`00000030 00000000`00000002 00000000`00000001 fffff800`028dd6ef ��������������������������������������������������������������������������������������`` by jcgriff2 J. C. Griffith, Microsoft MVP https://mvp.support.microsoft.com/profile/Griffith www.jcgriff2.com �������������������������������������������������������������������������������������� I did use the installation DVD when reinstalling Windows on the new hard drive. Going to try your KillDisk boot CD recommendation for now. I'll post back in a few once I reinstall Windows again.
While I wait (KillDisk is kind of a lengthy process for a 1TB hard drive)... is it possible that something may be corrupt on the Windows 7 OEM disc? Or with the motherboard itself?
So... I wiped the hard drive with the bootable KillDisk, but now I don't even think I'm able to reinstall Windows. I get to the beginning of the installation where it says "Setup is starting..." after I click "Install Now" and then I get a BSOD. I'll keep trying and post back if I have any success. Any ideas?
EDIT: I'm including some info about the crash during the Windows installation (since I can't really show dump files or error reports)...
An error has occurred and Windows has been shut down to prevent damage to your system...
PAGE_FAULT_IN_NONPAGED_AREA
Blah blah blah blah blah
Technical Information:
***STOP: 0x00000050 (0xFFFFF88003FACF90, 0x0000000000000000, 0xFFFFF8000CE7CA99, x0000000000000000
EDIT: I'm including some info about the crash during the Windows installation (since I can't really show dump files or error reports)...
An error has occurred and Windows has been shut down to prevent damage to your system...
PAGE_FAULT_IN_NONPAGED_AREA
Blah blah blah blah blah
Technical Information:
***STOP: 0x00000050 (0xFFFFF88003FACF90, 0x0000000000000000, 0xFFFFF8000CE7CA99, x0000000000000000
Got a little bit farther with the last attempt, but I keep getting crashes during installation.
OK. Let's assume you have a hardware problem.
Now disconnect anything and everything. Remove all boards. Remove all memory. Disconnect your monitor, your keyboard, your mouse.
Be sure the the case is off so you can observe if the fans are spiinning and also so you can listen for the beep codes.
Trust only the mobo manufacturer's manual for the meaning of the beep codes.
If you don't get one then you are really in trouble.
If the beep code says no memory, then stick in one stick. Keep adding memory upto what ever you have.
Keep working thru the bios codes. All this time you keep a close eye on those fans that they are spiinning. Keep the cover off of the the computer thru out this entire exercise.
More often than not, although the user doesn't believe it.... Heat is your big enemy.
Now disconnect anything and everything. Remove all boards. Remove all memory. Disconnect your monitor, your keyboard, your mouse.
Be sure the the case is off so you can observe if the fans are spiinning and also so you can listen for the beep codes.
Trust only the mobo manufacturer's manual for the meaning of the beep codes.
If you don't get one then you are really in trouble.
If the beep code says no memory, then stick in one stick. Keep adding memory upto what ever you have.
Keep working thru the bios codes. All this time you keep a close eye on those fans that they are spiinning. Keep the cover off of the the computer thru out this entire exercise.
More often than not, although the user doesn't believe it.... Heat is your big enemy.
Followed instructions in previous post to the tee... disconnected all external devices like mouse, keyboard, monitor, ethernet cable, speakers... basically everything internally from the motherboard (except the beeper, case's power button, cpu, and all fans).
With no externals hooked up to the I/O panel in the back, I received a single short beep (meaning system boots successfully). Took out the memory... With no memory inserted I received continuous long beeps (mobo's book says this means graphics card not inserted properly)... put memory back in and got a single short beep (meaning system boots successfully). With no graphics card inserted, I received one long beep, 2 short beeps (meaning monitor or graphics card error). The book doesn't give a very detailed list of beep codes, and I tried to search online for some and was unsuccessful... yes, even tried Gigabyte's website. Turns out that Gigabyte doesn't provide a detailed list of beep codes and a lot of other people have had trouble finding the same information. Here's all that the book gives me:
1 short: System boots successfully
2 short: CMOS setting error
1 long, 1 short: Memory or motherboard error
1 long, 2 short: Monitor or graphics card error
1 long, 3 short: Ketboard error
1 long, 9 short: BIOS ROM error
Continuous long beeps: Graphics card not inserted properly
Continuous short beeps: Power error
As far as heat goes, it's in a fairly cool environment with 3 fans running in the case (not including the 2 fans in the power supply). I remember looking at the CPU temperature in the BIOS and it said it was 47 degrees Celsius if I remember correctly.
With no externals hooked up to the I/O panel in the back, I received a single short beep (meaning system boots successfully). Took out the memory... With no memory inserted I received continuous long beeps (mobo's book says this means graphics card not inserted properly)... put memory back in and got a single short beep (meaning system boots successfully). With no graphics card inserted, I received one long beep, 2 short beeps (meaning monitor or graphics card error). The book doesn't give a very detailed list of beep codes, and I tried to search online for some and was unsuccessful... yes, even tried Gigabyte's website. Turns out that Gigabyte doesn't provide a detailed list of beep codes and a lot of other people have had trouble finding the same information. Here's all that the book gives me:
1 short: System boots successfully
2 short: CMOS setting error
1 long, 1 short: Memory or motherboard error
1 long, 2 short: Monitor or graphics card error
1 long, 3 short: Ketboard error
1 long, 9 short: BIOS ROM error
Continuous long beeps: Graphics card not inserted properly
Continuous short beeps: Power error
As far as heat goes, it's in a fairly cool environment with 3 fans running in the case (not including the 2 fans in the power supply). I remember looking at the CPU temperature in the BIOS and it said it was 47 degrees Celsius if I remember correctly.
Conveniently, my 30-day replacement for the motherboard from Newegg ran out last week; however, Gigabyte carries a 3-year warranty on their motherboards. Should I look into that? Or do you guys think I'll run into the same problems even with a new motherboard? I've ran the recommended hardware and memory tests and they've all come back clean. But I'm still having trouble with crashes simply installing Windows. Is this a problem with the Windows disc I received or something with the motherboard?
You have problems that are most likely to be hardware. As such, swapping the mobo would be a good idea if you can do it without charge.
It could also be the Windows disk - is it an original Microsoft disk (with the hologram?). Where did you get the disk from?
Checking compatibility for all installed hardware and software may help: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads
Hardware removal (as suggested above) is the easiest way to figure out what's wrong - but you'll eventually reach a point where you can't remove any more hardware. If that's the case, then you'll have to guess what (among the remaining hardware) is at fault. Don't forget to try installing windows on the stripped down system to see if it succeeds there.
It could also be the Windows disk - is it an original Microsoft disk (with the hologram?). Where did you get the disk from?
Checking compatibility for all installed hardware and software may help: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads
Hardware removal (as suggested above) is the easiest way to figure out what's wrong - but you'll eventually reach a point where you can't remove any more hardware. If that's the case, then you'll have to guess what (among the remaining hardware) is at fault. Don't forget to try installing windows on the stripped down system to see if it succeeds there.
�� Quote: Originally Posted by usasma It could also be the Windows disk - is it an original Microsoft disk (with the hologram?). Where did you get the disk from?
After multiple attempts at trying to reinstall Windows, I've totally given up. I can't make it to the beginning stages of the install before crashing. Perhaps replacing the motherboard will fix my crashing issues... but since no one (including Microsoft) offers replacement on software discs, I think I'm just stuck with buying a brand new copy of Windows 
If you have an OEM copy of Windows, no, Microsoft does not replace those - the OEM would have to. However, if you have a retail copy, you should indeed be able to (for a fee) call MS and get a new disc.
I've got an OEM version... should have spent the extra $50 and gotten the retail. As for replacement on this, I think I'm out of luck. But, do I replace the motherboard or the Windows disc?
Soooo....
After some more attempts at reinstalling, followed by crashing, I tried running Windows Memory Test (not sure how I ended up there, all the restarts are starting to blur together in my mind). On pass #2 it said there was a hardware issue detected. Since it was a memory test, I assumed it was referring to the memory... so I removed one of the memory sticks. I was able to restart and get the Windows installation to begin; however, I'm stuck at 0% on the "Expanding Windows files" stage. Questions/comments/ideas?
After some more attempts at reinstalling, followed by crashing, I tried running Windows Memory Test (not sure how I ended up there, all the restarts are starting to blur together in my mind). On pass #2 it said there was a hardware issue detected. Since it was a memory test, I assumed it was referring to the memory... so I removed one of the memory sticks. I was able to restart and get the Windows installation to begin; however, I'm stuck at 0% on the "Expanding Windows files" stage. Questions/comments/ideas?
STOP THE PRESS!!!
I guess I was a little impatient... previous tries at reinstallation led me to think that the "Expanding Windows files" stage shouldn't take that long to complete... but I'm back up and running with Windows successfully installed. As recommended in previous posts in this thread, I'll avoid installing third party files for a few days and check for system stability.
But!!! Does this mean that I should not install any drivers or run Windows Update (which in turn automatically installs third-party files such as drivers)??
I guess I was a little impatient... previous tries at reinstallation led me to think that the "Expanding Windows files" stage shouldn't take that long to complete... but I'm back up and running with Windows successfully installed. As recommended in previous posts in this thread, I'll avoid installing third party files for a few days and check for system stability.
But!!! Does this mean that I should not install any drivers or run Windows Update (which in turn automatically installs third-party files such as drivers)??
That's a great news. As if now turn off Windows Update just Download and install Microsoft security essentials to make sure your protected. Lets the System run like that for 2 or 3 days.
Will do, Captain. As for the faulty memory stick (I'm assuming for now that was my problem), I'm curious why it was not detected when previously running Windows Memory Diagnostic Tool or Memtest86+. Oh well... I'll post back in a few days and let you guys know what's up... or maybe sooner if something happens 
Thanks to everyone involved in helping with this issue!
Thanks to everyone involved in helping with this issue!
Edit:
Good news you got it installed.
Memtest86+ will usually find errors in your RAM but some errors may not occur until the system is stressed or it could be a (intermittent) faulty motherboard slot. Hopefully not the case.
Let us know how it's going.
�� Quote: Originally Posted by mzimmer4 If you want to try a new installation file.
You can D/L Win7 from the MS site and then you can just enter your own key when requested.
To control multiple activations, wait until your OS is stable before activating.
Burn to DVD or easier if you can put it on a minimum 4GB USB memory stick.
Take your pick, they all work easily.
USB Windows 7 Installation Key Drive - Create
How to Get and Use the Windows 7 USB/DVD Download Tool
Install Windows 7 from USB Pen Drive Using Grub4Dos
Good news you got it installed.
Memtest86+ will usually find errors in your RAM but some errors may not occur until the system is stressed or it could be a (intermittent) faulty motherboard slot. Hopefully not the case.
Let us know how it's going.
�� Quote: Originally Posted by mzimmer4 I've got an OEM version... should have spent the extra $50 and gotten the retail. As for replacement on this, I think I'm out of luck. But, do I replace the motherboard or the Windows disc?
You can D/L Win7 from the MS site and then you can just enter your own key when requested.
To control multiple activations, wait until your OS is stable before activating.
Burn to DVD or easier if you can put it on a minimum 4GB USB memory stick.
Take your pick, they all work easily.
USB Windows 7 Installation Key Drive - Create
How to Get and Use the Windows 7 USB/DVD Download Tool
Install Windows 7 from USB Pen Drive Using Grub4Dos
Thanks Dave... this is good info to know. I've read in many places about people installing Windows 7 from USB or CD sources and never knew how they got them.
The USB memory stick method is easy to do and a much faster way to run the installation.
I've been using it for about a year now, and it's great.
I've been using it for about a year now, and it's great.
Hi -
If problems creep up again, to help ascertain if the Windows 7 installation DVD you have is corrupted in some manner and causing trouble, I suggest that you install the Windows 7 Enterprise Edition 90-day trial version. You can download the ISO directly from Microsoft and burn it to DVD.
Windows 7 Enterprise | Trial, Evaluation, Test, Download
Use KillDisk on the HDD prior to installation.
If you encounter similar problems installing the Windows 7 Enterprise Edition, then hardware must be scrutinized more closely.
BSODs occur under Windows. The BSOD you reported had a bugcheck = 0x50 = invalid memory referenced.
Meanwhile, I would allow ALL Windows Updates to come in.
www.update.microsoft.com
Regards. . .
jcgriff2
`
If problems creep up again, to help ascertain if the Windows 7 installation DVD you have is corrupted in some manner and causing trouble, I suggest that you install the Windows 7 Enterprise Edition 90-day trial version. You can download the ISO directly from Microsoft and burn it to DVD.
Windows 7 Enterprise | Trial, Evaluation, Test, Download
Use KillDisk on the HDD prior to installation.
If you encounter similar problems installing the Windows 7 Enterprise Edition, then hardware must be scrutinized more closely.
BSODs occur under Windows. The BSOD you reported had a bugcheck = 0x50 = invalid memory referenced.
Meanwhile, I would allow ALL Windows Updates to come in.
www.update.microsoft.com
Regards. . .
jcgriff2
`
Whoops, another crash! Wasn't doing anything at all... I got Windows to successfully install, and was just going to leave it idling for a day or two with no activity. Here are some attachments for the pro's to look at. Keep in mind that after the install of Windows, I didn't install anything, including drivers. It was a barebone install of the OS to check system stability.
0x50- Probably Caused By hardware.
Update your Realtek network adapter drivers: Realtek
Update your ATI drivers: https://a248.e.akamai.net/f/674/9206...win7_64_dd.exe
...Summary of the Dumps:
Update your Realtek network adapter drivers: Realtek
Update your ATI drivers: https://a248.e.akamai.net/f/674/9206...win7_64_dd.exe
...Summary of the Dumps:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sun Aug 29 01:15:40.813 2010 (UTC - 4:00) System Uptime: 0 days 0:10:48.910 BugCheck 50, {ffffffffffffff8b, 1, fffff800028ce1af, 0} Probably caused by : hardware ( nt!ExAcquireResourceExclusiveLite+142 ) BUGCHECK_STR: 0x50 PROCESS_NAME: System �������������������������������������������������������������������������������������� �� Quote: Originally Posted by mzimmer4 So... after switching out the SATA cable with one supplied with the motherboard, I finally got my computer to turn back on (after having some grounding issues with the motherboard and chassis). The problem still exists though. Upon rebooting, I encountered 4 or 5 BSODs and finally got Windows to boot up as it should. Included are some more perfmon reports and dump files.
Also, before I changed out the SATA cable, I ran Memtest86+ and also Seatools for Windows. On the plus side, both checked out good (whereas the hard drive check failed miserably with the previous hard drive). Seems like my hardware is in good shape. You guys definitely know your diagnostics, I'll give you that. Please help before I jab a pencil in my ear!
Also, before I changed out the SATA cable, I ran Memtest86+ and also Seatools for Windows. On the plus side, both checked out good (whereas the hard drive check failed miserably with the previous hard drive). Seems like my hardware is in good shape. You guys definitely know your diagnostics, I'll give you that. Please help before I jab a pencil in my ear!
You should have the HDD SATA cable plugged into SATA port 0, the CD/DVD can be plugged into any other port but recommended to use the last port.
�� Quote: Originally Posted by mzimmer4 Followed instructions in previous post to the tee... disconnected all external devices like mouse, keyboard, monitor, ethernet cable, speakers... basically everything internally from the motherboard (except the beeper, case's power button, cpu, and all fans).
With no externals hooked up to the I/O panel in the back, I received a single short beep (meaning system boots successfully).
With no externals hooked up to the I/O panel in the back, I received a single short beep (meaning system boots successfully).
Is the above with nothing connected externally and everything still connected to the motherboard inside the case?
(Obviously, just to confirm)
Is the CD/DVD cable still connected?
If this is correct, what do you normally connect externally?
Keyboard, Mouse, Monitor, and?
�� Quote: Originally Posted by mzimmer4 Took out the memory... With no memory inserted I received continuous long beeps (mobo's book says this means graphics card not inserted properly)...
�� Quote: Originally Posted by mzimmer4 put memory back in and got a single short beep (meaning system boots successfully). With no graphics card inserted, I received one long beep, 2 short beeps (meaning monitor or graphics card error). The book doesn't give a very detailed list of beep codes, and I tried to search online for some and was unsuccessful... yes, even tried Gigabyte's website. Turns out that Gigabyte doesn't provide a detailed list of beep codes and a lot of other people have had trouble finding the same information. Here's all that the book gives me:
1 short: System boots successfully
2 short: CMOS setting error
1 long, 1 short: Memory or motherboard error
1 long, 2 short: Monitor or graphics card error
1 long, 3 short: Ketboard error
1 long, 9 short: BIOS ROM error
Continuous long beeps: Graphics card not inserted properly
Continuous short beeps: Power error
As far as heat goes, it's in a fairly cool environment with 3 fans running in the case (not including the 2 fans in the power supply). I remember looking at the CPU temperature in the BIOS and it said it was 47 degrees Celsius if I remember correctly.
1 short: System boots successfully
2 short: CMOS setting error
1 long, 1 short: Memory or motherboard error
1 long, 2 short: Monitor or graphics card error
1 long, 3 short: Ketboard error
1 long, 9 short: BIOS ROM error
Continuous long beeps: Graphics card not inserted properly
Continuous short beeps: Power error
As far as heat goes, it's in a fairly cool environment with 3 fans running in the case (not including the 2 fans in the power supply). I remember looking at the CPU temperature in the BIOS and it said it was 47 degrees Celsius if I remember correctly.
Seems a bit high.
Check your temps with Core Temp.
Did you assemble the computer?
Stock CPU cooler?
What case and cooling fans?
�� Quote: Originally Posted by Dave76 What were the grounding issues?
�� Quote: Originally Posted by Dave76 You should have the HDD SATA cable plugged into SATA port 0, the CD/DVD can be plugged into any other port but recommended to use the last port.
�� Quote: Originally Posted by Dave76 Do you get a single short beep with everything connected internally and externally?
Is the above with nothing connected externally and everything still connected to the motherboard inside the case?
(Obviously, just to confirm)
Is the CD/DVD cable still connected?
Is the above with nothing connected externally and everything still connected to the motherboard inside the case?
(Obviously, just to confirm)
Is the CD/DVD cable still connected?
�� Quote: Originally Posted by Dave76 If this is correct, what do you normally connect externally?
Keyboard, Mouse, Monitor, and?
Keyboard, Mouse, Monitor, and?
�� Quote: Originally Posted by Dave76 �� Quote: Originally Posted by Dave76 Did you assemble the computer?
Stock CPU cooler?
What case and cooling fans?
Stock CPU cooler?
What case and cooling fans?
CPU temp is currently 29-35 degrees Celsius. ...checked with CoreTemp 0.99.7
This question is important.
Do you get a single short beep with everything connected internally and externally?
Normal use scenario.
Good job answering the questions.
The temps are in range.
Most AMD temps I've seen are usually the same for all and a little lower.
We might come back to this.
Check the temps next time you run Memtest86+ or Prime95, let us know the results.
Give Prime95 torture test - blend, a quick run, just until the temps stabilize.
Do you get a single short beep with everything connected internally and externally?
Normal use scenario.
Good job answering the questions.
The temps are in range.
Most AMD temps I've seen are usually the same for all and a little lower.
We might come back to this.
Check the temps next time you run Memtest86+ or Prime95, let us know the results.
Give Prime95 torture test - blend, a quick run, just until the temps stabilize.
�� Quote: Originally Posted by Dave76 This question is important.
Do you get a single short beep with everything connected internally and externally?
Normal use scenario.
Good job answering the questions.
The temps are in range.
Most AMD temps I've seen are usually the same for all and a little lower.
We might come back to this.
Check the temps next time you run Memtest86+ or Prime95, let us know the results.
Give Prime95 torture test - blend, a quick run, just until the temps stabilize.
Do you get a single short beep with everything connected internally and externally?
Normal use scenario.
Good job answering the questions.
The temps are in range.
Most AMD temps I've seen are usually the same for all and a little lower.
We might come back to this.
Check the temps next time you run Memtest86+ or Prime95, let us know the results.
Give Prime95 torture test - blend, a quick run, just until the temps stabilize.
Also, everything has been running fairly stable for the past 36 hours or so. I turned off the computer several times and it has been able to boot back up with no halts or crashes. But, I was beginning an installation for Wow.exe earlier today, and I received a generic error and some screen flashing/freezing. The computer restarted itself and CHKDSK ran following a restart (seemed to edit some bad files or something). I was starting to suspect a video card error, since when I tried to access the BIOS screen, it was just a bunch of wierd illegible characters. Everything seems to be back to normal now though, as long as I don't do anything :P
Yes, I believe the graphics drivers were installed with Windows Update. But, I did experience a crash earlier today... also there's still the complication with installing Wow. I was able to install the full-version game client from Battle.net before on the original setup with no errors (when the computer was first completed). Attached are some dump files and a perfmon report... let me know what you guys think. Something's still not right... even though I've just been running a minimal setup. Perhaps something I never configured in BIOS maybe? Not sure, like the first post suggests, this is my first build and I'm not too experienced.
I would get your graphics drivers from the ATI website linked by Jonathan_King in post#45.
K, I'll try that... Also, I was looking over the performance report and noticed that it has drivers missing for "Universal Serial Bus (USB) Controller". But, my USB ports seem to be working just fine. Could this be drivers for the 3.0 ports? Didn't know if this made a big difference. Anyhow, I'll get to the graphics drivers and post back if any problems arise. Thanks again guys.
So, I recently had another random crash. Everything was running fine for a couple weeks until this. It crashed 3 times in about 15 minutes. Here are some dump files and a performance monitor report. Let me know what you guys can find. Thanks
Install this Realtek driver: Realtek
Install this chipset driver: http://download.gigabyte.us/FileList...eries_win7.exe
After you install the chipset drivers, run a CPU stress test, keeping an eye one temps: http://www.sevenforums.com/tutorials...t-prime95.html
Finally, let's run a RAM test again. RAM - Test with Memtest86+
...Summary of the Dumps:
Install this chipset driver: http://download.gigabyte.us/FileList...eries_win7.exe
After you install the chipset drivers, run a CPU stress test, keeping an eye one temps: http://www.sevenforums.com/tutorials...t-prime95.html
Finally, let's run a RAM test again. RAM - Test with Memtest86+
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Sep 17 21:54:11.284 2010 (UTC - 4:00) System Uptime: 0 days 0:00:56.814 BugCheck 1E, {0, 0, 0, 0} Probably caused by : amdppm.sys ( amdppm!C1Halt+2 ) BUGCHECK_STR: 0x1E_0 PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Sep 17 21:52:48.258 2010 (UTC - 4:00) System Uptime: 0 days 0:01:06.162 BugCheck 1, {76fbfeba, 0, ffffffff, fffff880057ddca0} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 ) BUGCHECK_STR: 0x1 PROCESS_NAME: svchost.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Sep 17 21:51:13.850 2010 (UTC - 4:00) System Uptime: 0 days 1:28:59.754 BugCheck 1E, {0, 0, 0, 0} Probably caused by : amdppm.sys ( amdppm!C1Halt+2 ) BUGCHECK_STR: 0x1E_0 PROCESS_NAME: System �������������������������������������������������������������������������������������� Ok, I installed the Realtek drivers, but I'm not sure about the chipset drivers. I extracted the folder to my desktop, but where exactly in the Device Manager do I go to update the one for the chipset? Thanks again.
Just thought of something... when you said "Install this Realtek driver", you were referring to the Realtek network adapter, correct? That's the driver I updated. Didn't really think too much about it, but I've always associated Realtek with network adapters, but I understand it can relate to other things. If you weren't referring to drivers for the network adapter, let me know where I screwed up and how I can fix it. Still confused about the chipset driver (see previous post).
Yeah, I was referring to your Realtek Network Adapter drivers. I should have specified, sorry.
If you extracted the .exe file you downloaded (the 100MB one), go to the extracted location and run Setup.exe.
If you extracted the .exe file you downloaded (the 100MB one), go to the extracted location and run Setup.exe.
Soooooo... I'm back yet again. Here's the story... installed the drivers that Jonathan recommended (ATI & Realtek). Good news is that the performance monitor report doesn't show me with outdated drivers anymore. So I think that part is good.
But!!! I've started running into another wierd problem, involving more BSODs and random freezings. After the computer was sitting for a few hours, I was going to play WoW and after opening the game, the computer restarted itself and started emitting long beeps (3 long... pause... 3 long... pause... etc.) Neither the Gigabyte website nor the manual gives any indication as to what this means. The beeping always happens before the BIOS screen even comes up.
The problem seems to be sporadic though... that is, it will happen sometimes, but sometimes it boots up and runs just fine (boots past BIOS and into Windows desktop). Recently ran Memtest86+ through 4 passes with no errors.
So my question is this... do I have a problem with my motherboard? Possibly the CPU? Could it be some BIOS settings that I never configured? Any help is greatly appreciated. Attached are more dumps and the perfmon report. Thanks guys!
But!!! I've started running into another wierd problem, involving more BSODs and random freezings. After the computer was sitting for a few hours, I was going to play WoW and after opening the game, the computer restarted itself and started emitting long beeps (3 long... pause... 3 long... pause... etc.) Neither the Gigabyte website nor the manual gives any indication as to what this means. The beeping always happens before the BIOS screen even comes up.
The problem seems to be sporadic though... that is, it will happen sometimes, but sometimes it boots up and runs just fine (boots past BIOS and into Windows desktop). Recently ran Memtest86+ through 4 passes with no errors.
So my question is this... do I have a problem with my motherboard? Possibly the CPU? Could it be some BIOS settings that I never configured? Any help is greatly appreciated. Attached are more dumps and the perfmon report. Thanks guys!
Computer wouldn't even turn on earlier... got no beeps and no POST/BIOS screens. Removed the #2 stick... got the beeps but nothing on screen.
After tinkering around and moving memory (testing one stick at a time... one slot at a time), I've managed to turn on the computer with only one stick in the #2 slot. Is it possible that I have a memory problem that's not being picked up by Memtest86+? G.Skill has a lifetime warranty on their memory, so I might try just getting these replaced.
But I don't know if the sticks are the problem, or if it's the ports on the board. One thing for sure, moving memory around or removing a stick definitely makes a difference when it won't boot up (long beeps, see previous post).
After tinkering around and moving memory (testing one stick at a time... one slot at a time), I've managed to turn on the computer with only one stick in the #2 slot. Is it possible that I have a memory problem that's not being picked up by Memtest86+? G.Skill has a lifetime warranty on their memory, so I might try just getting these replaced.
But I don't know if the sticks are the problem, or if it's the ports on the board. One thing for sure, moving memory around or removing a stick definitely makes a difference when it won't boot up (long beeps, see previous post).
Không có nhận xét nào:
Đăng nhận xét