Can someone help with Win7 x64 BSOD's and Spontaneous Reboots on HP Elite 8100 i5-660 & 16GB SDRAM?
I have a nice new shiny HP Elite 8100. I installed Windows 7 x64 Enterprise and I found sporatic spontaneous reboots. I have made some hardware changes like adding two Samsung 128GB Solid State Drives and 16GB of Kingston SDRAM. Since the beginning of this process I have 1) Switched the 8100 box for another all together - Spontaneous reboots continued 2) Replaced the 16GB (4x4GB) Kingston Memory after running repeated memory diagnostics with 16GB Corsair memory (4x4GB) - Spontaneous reboots continued 3) Replaced the two 128GB Samsung Solid State Drives with two new 120GB OCZ Vertex 2 Solid State Drives - Spontaneous reboots continued 4) Recieved and reinstalled HP original Win7 x64 Pro from HP Quick Restore discs just last night - within the first 15 minutes of using it today, and having NOT installed any software yet it Blue Screened. Before it often just rebooted with no opportunity to Blue Screen. This time I was able to get the details from the event viewer. Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 22/03/2011 1:16:10 PM Event ID: 1001 Task Category: None Level: Error Keywords: Classic User: N/A Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002ac5b9f, 0xfffff880027589c0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 032211-10764-01. Which led me to here. I see a number of people who have the know how to read and identify problems from the memory dump file. If anyone can help me narrow down what's wrong I would be most grateful. Memory Dump uploaded to Skydrive: http://cid-3326fde67cde1cbf.office.live.com/self.aspx/Public/032211-10764-01.zip CPU-Z report (screen caps in RTF) uploaded here: http://cid-3326fde67cde1cbf.office.live.com/self.aspx/Public/28095-DEREKO%20-%20CPU-Z.zip I also have an HP nVidia Quadro VNS 295 that I am thinking of using. So maybe using that card with the latest drivers will help fix the problem. Hope so, I have spent a bundle already trying different hardware. So any help you can provide from the memory dump about the source of the problem would be VERY much appreciated. Thanks much - Derek
March 23rd, 2011 10:16pm

SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck STACK_TEXT: nt!SeAccessCheckWithHint+0x10f this tells me nothing usefull. Configure your Windows to create a kernel dump [1] and upload the zipped dump (C:\Windows\memory.dmp) to your SkyDrive and post a link here after the PC still crashes again. Do the crashes also occur if you use less RAM (8 or 12GB)? Does the HP board support Corsair RAMs? André [1] http://www.brighthub.com/computing/windows-platform/articles/81867.aspx"A programmer is just a tool which converts caffeine into code" Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2011 10:32am

Hi, Did your issue solved by the suggestion of Andre? Please feel free to give me any update. Thanks. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 28th, 2011 8:22am

Hi, Did your issue solved by the suggestion of Andre? Please feel free to give me any update. Thanks. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
March 28th, 2011 8:22am

http://cid-3326fde67cde1cbf.office.live.com/self.aspx/Public/2011-03-23-1825hrs.zipx http://cid-3326fde67cde1cbf.office.live.com/self.aspx/Public/2011-03-28-1002hrs.zipx Status: I installed an nVidia Quatro NVS 295 video card which I was planning to use anyway. Things seemed to go smooth for a few days. And just as I was zipping up the memory.dmp file the BSOD hit again. THe bugcheck code seems to be different every time too. So I have two instances available at the above links. I had to use zipx to get it to fit under 50MB for skydrive. When this was initially happening I was using Kingston Memory specifically certified for use on this unit. The Corsair is the same type and model of RAM, but I don't think it is specifically named as compatible. But I have the exact same memory in another box and it hasn't experienced this. I have swapped the whole 8100 box once already trying to rule out the core system. I'm thinking of trying a third 8100 box, start from scratch with Win7 x64 Enterprise SP1 but I have no indication doing so will be any different. Any help narrowing down the true source of the problem would be so very much appreciated. Derek
March 28th, 2011 9:49pm

http://cid-3326fde67cde1cbf.office.live.com/self.aspx/Public/2011-03-23-1825hrs.zipx http://cid-3326fde67cde1cbf.office.live.com/self.aspx/Public/2011-03-28-1002hrs.zipx Status: I installed an nVidia Quatro NVS 295 video card which I was planning to use anyway. Things seemed to go smooth for a few days. And just as I was zipping up the memory.dmp file the BSOD hit again. THe bugcheck code seems to be different every time too. So I have two instances available at the above links. I had to use zipx to get it to fit under 50MB for skydrive. When this was initially happening I was using Kingston Memory specifically certified for use on this unit. The Corsair is the same type and model of RAM, but I don't think it is specifically named as compatible. But I have the exact same memory in another box and it hasn't experienced this. I have swapped the whole 8100 box once already trying to rule out the core system. I'm thinking of trying a third 8100 box, start from scratch with Win7 x64 Enterprise SP1 but I have no indication doing so will be any different. Any help narrowing down the true source of the problem would be so very much appreciated. Derek
Free Windows Admin Tool Kit Click here and download it now
March 28th, 2011 9:49pm

2011-03-28-1002hrs: Bug Check 0x4E: PFN_LIST_CORRUPT This indicates that the page frame number (PFN) list is corrupted. http://msdn.microsoft.com/en-us/library/ff559014%28VS.85%29.aspx fffff880`0350fab8 fffff800`02ca16be nt!KeBugCheckEx fffff880`0350fac0 fffff800`02cb6c40 nt!MiUnlinkPageFromLockedList+0x8e fffff880`0350fb50 fffff800`02cb7a6c nt!MiGatherMappedPages+0x108 fffff880`0350fc50 fffff800`02f24c06 nt!MiMappedPageWriter+0x198 fffff880`0350fd40 fffff800`02c5ec26 nt!PspSystemThreadStartup+0x5a fffff880`0350fd80 00000000`00000000 nt!KxStartSystemThread+0x16 2011-03-23-1825hrs: Bug Check 0x24: NTFS_FILE_SYSTEM This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives. fffff880`033911c8 fffff880`01426b68 nt!KeBugCheckEx fffff880`033911d0 fffff880`0143ab79 Ntfs! ?? ::FNODOBFM::`string'+0x2b19 fffff880`03391210 fffff800`02ae7d1c Ntfs! ?? ::FNODOBFM::`string'+0x12a6 fffff880`03391250 fffff880`0143a9d5 nt!_C_specific_handler+0x8c fffff880`033912c0 fffff800`02adf40d Ntfs!_GSHandlerCheck_SEH+0x75 fffff880`033912f0 fffff800`02ae6a90 nt!RtlpExecuteHandlerForException+0xd fffff880`03391320 fffff800`02af39ef nt!RtlDispatchException+0x410 fffff880`03391a00 fffff800`02ab8d82 nt!KiDispatchException+0x16f fffff880`03392090 fffff800`02ab6edf nt!KiExceptionDispatch+0xc2 fffff880`03392270 fffff880`0142e0d0 nt!KiInvalidOpcodeFault+0x11f fffff880`03392400 fffff880`0142dba6 Ntfs!NtfsLookupAllocation+0x70 fffff880`03392570 fffff880`0142eedb Ntfs!NtfsPrepareSimpleBuffers+0x146 fffff880`03392630 fffff880`0142cd5c Ntfs!NtfsPrepareBuffers+0xcb fffff880`033926b0 fffff880`0143c250 Ntfs!NtfsNonCachedIo+0x1bc fffff880`03392880 fffff880`01435b62 Ntfs!NtfsNonCachedUsaWrite+0x64 fffff880`03392910 fffff880`01438663 Ntfs!NtfsCommonWrite+0x2c4b fffff880`03392ac0 fffff880`012d623f Ntfs!NtfsFsdWrite+0x1c3 fffff880`03392d40 fffff880`012d46df fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`03392dd0 fffff800`02aa82ff fltmgr!FltpDispatch+0xcf fffff880`03392e30 fffff800`02aa7987 nt!IoSynchronousPageWrite+0x24f fffff880`03392eb0 fffff800`02aa5954 nt!MiFlushSectionInternal+0xa58 fffff880`033930f0 fffff800`02aa54fa nt!MmFlushSection+0x1f4 fffff880`033931b0 fffff880`0143bccc nt!CcFlushCache+0x88a fffff880`033932b0 fffff880`014e7cdf Ntfs!LfsFlushLfcb+0x644 fffff880`03393430 fffff880`014b7db0 Ntfs!LfsFlushToLsnPriv+0x143 fffff880`033934c0 fffff880`014b6867 Ntfs!LfsWriteLfsRestart+0xe8 fffff880`03393500 fffff880`014b5827 Ntfs!LfsWriteRestartArea+0x143 fffff880`03393590 fffff880`014b77db Ntfs!NtfsCheckpointVolume+0xa97 fffff880`03393990 fffff880`014b799b Ntfs!NtfsCheckpointAllVolumesWorker+0x4b fffff880`033939e0 fffff880`014b6a28 Ntfs!NtfsForEachVcb+0x167 fffff880`03393a80 fffff800`02ac6961 Ntfs!NtfsCheckpointAllVolumes+0xb8 fffff880`03393cb0 fffff800`02d5dc06 nt!ExpWorkerThread+0x111 fffff880`03393d40 fffff800`02a97c26 nt!PspSystemThreadStartup+0x5a fffff880`03393d80 00000000`00000000 nt!KxStartSystemThread+0x16 CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs 14 errors : !Ntfs (fffff8800142e0c0-fffff880015160f8) fffff8800142e0c0 *04 00 00 44 88 bc 24 98 *09 00 00 c6 44 24 50 00 ...D..$.....D$P. fffff8800142e0d0 *ce 44 24 51 00 48 8b 41 40 80 78 18 0d 0f 84 fc .D$Q.H.A@.x..... fffff8800142e0e0 0b 00 00 c6 44 24 54 00 *49 8b 8a 50 01 00 00 ff ....D$T.I..P.... fffff8800142e0f0 15 bb 8b 03 00 45 33 d2 *40 8b d2 44 8b 8f 3c 01 .....E3.@..D..<. ... fffff880014a60d0 ff e9 07 f0 ff ff 44 8a *b4 24 b1 00 00 00 e9 fa ......D..$...... fffff880014a60e0 ef ff ff 44 8a bc 24 b1 *01 00 00 e9 ed ef ff ff ...D..$......... fffff880014a60f0 *45 8a bc 24 b1 00 00 00 *e8 e0 ef ff ff 41 b8 5d E..$.........A.] ... fffff880015160c0 *f5 e9 26 e5 fb ff 41 f6 *8d 44 01 00 00 10 0f 84 ..&...A..D...... fffff880015160d0 *6d bb fb ff 45 8b 65 58 45 23 e7 0f 84 58 bb fb m...E.eXE#...X.. fffff880015160e0 ff 8b c8 41 2b cc 8b c1 *4d 03 d0 e9 49 bb fb ff ...A+...M...I... fffff880015160f0 85 c9 74 1c 8b c1 49 3b *44 68 74 0c 44 3b f1 76 ..t...I;Dht.D;.v MODULE_NAME: memory_corruption Does it happen with a traditional HDD, too? Also does the crash happen if you use less RAM (4,8,12GB)? The NTFS.sys driver is damaged in the RAM. Run sfc /scannow to see if the file is damaged on the disk, too. "A programmer is just a tool which converts caffeine into code" Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
March 29th, 2011 12:00am

2011-03-28-1002hrs: Bug Check 0x4E: PFN_LIST_CORRUPT This indicates that the page frame number (PFN) list is corrupted. http://msdn.microsoft.com/en-us/library/ff559014%28VS.85%29.aspx fffff880`0350fab8 fffff800`02ca16be nt!KeBugCheckEx fffff880`0350fac0 fffff800`02cb6c40 nt!MiUnlinkPageFromLockedList+0x8e fffff880`0350fb50 fffff800`02cb7a6c nt!MiGatherMappedPages+0x108 fffff880`0350fc50 fffff800`02f24c06 nt!MiMappedPageWriter+0x198 fffff880`0350fd40 fffff800`02c5ec26 nt!PspSystemThreadStartup+0x5a fffff880`0350fd80 00000000`00000000 nt!KxStartSystemThread+0x16 2011-03-23-1825hrs: Bug Check 0x24: NTFS_FILE_SYSTEM This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives. fffff880`033911c8 fffff880`01426b68 nt!KeBugCheckEx fffff880`033911d0 fffff880`0143ab79 Ntfs! ?? ::FNODOBFM::`string'+0x2b19 fffff880`03391210 fffff800`02ae7d1c Ntfs! ?? ::FNODOBFM::`string'+0x12a6 fffff880`03391250 fffff880`0143a9d5 nt!_C_specific_handler+0x8c fffff880`033912c0 fffff800`02adf40d Ntfs!_GSHandlerCheck_SEH+0x75 fffff880`033912f0 fffff800`02ae6a90 nt!RtlpExecuteHandlerForException+0xd fffff880`03391320 fffff800`02af39ef nt!RtlDispatchException+0x410 fffff880`03391a00 fffff800`02ab8d82 nt!KiDispatchException+0x16f fffff880`03392090 fffff800`02ab6edf nt!KiExceptionDispatch+0xc2 fffff880`03392270 fffff880`0142e0d0 nt!KiInvalidOpcodeFault+0x11f fffff880`03392400 fffff880`0142dba6 Ntfs!NtfsLookupAllocation+0x70 fffff880`03392570 fffff880`0142eedb Ntfs!NtfsPrepareSimpleBuffers+0x146 fffff880`03392630 fffff880`0142cd5c Ntfs!NtfsPrepareBuffers+0xcb fffff880`033926b0 fffff880`0143c250 Ntfs!NtfsNonCachedIo+0x1bc fffff880`03392880 fffff880`01435b62 Ntfs!NtfsNonCachedUsaWrite+0x64 fffff880`03392910 fffff880`01438663 Ntfs!NtfsCommonWrite+0x2c4b fffff880`03392ac0 fffff880`012d623f Ntfs!NtfsFsdWrite+0x1c3 fffff880`03392d40 fffff880`012d46df fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`03392dd0 fffff800`02aa82ff fltmgr!FltpDispatch+0xcf fffff880`03392e30 fffff800`02aa7987 nt!IoSynchronousPageWrite+0x24f fffff880`03392eb0 fffff800`02aa5954 nt!MiFlushSectionInternal+0xa58 fffff880`033930f0 fffff800`02aa54fa nt!MmFlushSection+0x1f4 fffff880`033931b0 fffff880`0143bccc nt!CcFlushCache+0x88a fffff880`033932b0 fffff880`014e7cdf Ntfs!LfsFlushLfcb+0x644 fffff880`03393430 fffff880`014b7db0 Ntfs!LfsFlushToLsnPriv+0x143 fffff880`033934c0 fffff880`014b6867 Ntfs!LfsWriteLfsRestart+0xe8 fffff880`03393500 fffff880`014b5827 Ntfs!LfsWriteRestartArea+0x143 fffff880`03393590 fffff880`014b77db Ntfs!NtfsCheckpointVolume+0xa97 fffff880`03393990 fffff880`014b799b Ntfs!NtfsCheckpointAllVolumesWorker+0x4b fffff880`033939e0 fffff880`014b6a28 Ntfs!NtfsForEachVcb+0x167 fffff880`03393a80 fffff800`02ac6961 Ntfs!NtfsCheckpointAllVolumes+0xb8 fffff880`03393cb0 fffff800`02d5dc06 nt!ExpWorkerThread+0x111 fffff880`03393d40 fffff800`02a97c26 nt!PspSystemThreadStartup+0x5a fffff880`03393d80 00000000`00000000 nt!KxStartSystemThread+0x16 CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs 14 errors : !Ntfs (fffff8800142e0c0-fffff880015160f8) fffff8800142e0c0 *04 00 00 44 88 bc 24 98 *09 00 00 c6 44 24 50 00 ...D..$.....D$P. fffff8800142e0d0 *ce 44 24 51 00 48 8b 41 40 80 78 18 0d 0f 84 fc .D$Q.H.A@.x..... fffff8800142e0e0 0b 00 00 c6 44 24 54 00 *49 8b 8a 50 01 00 00 ff ....D$T.I..P.... fffff8800142e0f0 15 bb 8b 03 00 45 33 d2 *40 8b d2 44 8b 8f 3c 01 .....E3.@..D..<. ... fffff880014a60d0 ff e9 07 f0 ff ff 44 8a *b4 24 b1 00 00 00 e9 fa ......D..$...... fffff880014a60e0 ef ff ff 44 8a bc 24 b1 *01 00 00 e9 ed ef ff ff ...D..$......... fffff880014a60f0 *45 8a bc 24 b1 00 00 00 *e8 e0 ef ff ff 41 b8 5d E..$.........A.] ... fffff880015160c0 *f5 e9 26 e5 fb ff 41 f6 *8d 44 01 00 00 10 0f 84 ..&...A..D...... fffff880015160d0 *6d bb fb ff 45 8b 65 58 45 23 e7 0f 84 58 bb fb m...E.eXE#...X.. fffff880015160e0 ff 8b c8 41 2b cc 8b c1 *4d 03 d0 e9 49 bb fb ff ...A+...M...I... fffff880015160f0 85 c9 74 1c 8b c1 49 3b *44 68 74 0c 44 3b f1 76 ..t...I;Dht.D;.v MODULE_NAME: memory_corruption Does it happen with a traditional HDD, too? Also does the crash happen if you use less RAM (4,8,12GB)? The NTFS.sys driver is damaged in the RAM. Run sfc /scannow to see if the file is damaged on the disk, too. "A programmer is just a tool which converts caffeine into code" Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2011 12:00am

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 7th, 2011 10:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics